I am using parse.com and my app is in production mode. and I have an issue with push notifications for IOS.
most of the times it works fine but sometimes it show "Another Error Occurred" in push notification explorer with the status sent. But users not getting push notification as they were supposed to get.
So how can I trace what is the reason behind and how can I fix this?
it's not certificate related issue as I have already changed my certificate on parse.com, and if it was certificate issue it should occurred each time.
does anyone have any idea how to fix this?
Related
After connecting Slack to Azure Bot Service following instruction from the link, Azure does not bypass the message to bot server. Sreenshots are from Issue which appears by clicking on issue button next to the channel. Issue appears every time I send message from Slack.
Anyone encountered similar case?
Error message is little unkind...
https://learn.microsoft.com/en-us/azure/bot-service/bot-service-channel-connect-slack?view=azure-bot-service-4.0&tabs=abs
BTW, test chat on portal is working as expected.
Triple checking my tokens, it fixed error. So it seems to be my mistake on setting token...
When error message spotted out credential error, it would have made my life easier...
I occasionally got this error in chrome console log POST https://example.com/example 0 ()
There's no information at all about the error.
What it is mean?
How to see more information about the error and how to deal with it?
Thanks in advance
I am not sure what is this caused by. I am getting it sometimes too. But the error is gone when I reconnect to the internet.
EDIT:
This error is shown when there is no internet connection. For me the issue was that I was subscribing to the network connection and was doing call right on the event which was giving me mentioned error. I found out that this is too soon even if event on connected was already triggered and web app is not yet connected. Delay one second after the event solved this for me. My project is Angular Ionic android / iOS app.
I'm trying to send a notification via C# SDK. I'm sending notifications for iOS.
string payload = "{\"aps\" : { \"alert\" : \"Message received from Bob\" }}";
var outcome = hub.SendAppleNativeNotificationAsync(payload, new[] { "b6a5d9c3-4297-422f-9a8d-b7979c30a5f8" }).GetAwaiter().GetResult();
Registration works fine, I can retrieve registered users, but I receive errors on sending. The error message is
Contract mismatch between ServiceBus and the Push Notification System
I've looked into manage.windowsazure.com for monitoring and saw that there were errors of type “Bad channel error”.
I assume that I should try to change my region for NH and probably the problem will go away, but is there anything else I could look at to resolve this issue?
Forgot to mention that everything was working on the first day I started to work with push notifications and only after several days became broken without any changes.
you may have open port 2135 and also add APN certificate
I didn't figured out what does that error mean but at least found the root cause. It was Testflight that by some obscure reasons uses production gateways to send notifications and not sandbox, and my NH has been configured with sandbox certificate, that's why it didn't work.
Early on in developing an iOS app with Xamarin, another developer and I got push notifications working for it using the Azure Messaging Component. It's a few months later now, and sometime between then and now, the push notifications stopped working. The code is still basically the same as before (which is nearly identical to the example code for the component), it was just moved to its own class for maintainability.
On Hub.UnregisterAllAsync(DeviceToken, error =>, error is:
The operation couldn’t be completed. (NSURLErrorDomain error -1012.)
On Hub.RegisterNativeAsync(DeviceToken, tags, error =>, error is:
URLRequest failed for <NSMutableURLRequest: 0x167dbd80>
{ URL: https://[our namespace].servicebus.windows.net/[our hub name]/Registrations/?$filter=deviceToken+eq+'[long token]'&api-version=2013-04 }
with status code: unauthorized
We tried a new hub, and a new namespace with a new hub, but without luck. I've rolled back the changes we've made since it was working, but with no luck there either. The same error happens on multiple devices, on multiple networks. It never shows any errors in the portal for APNS, so I'm assuming this is something with authenticating to the Hub itself. What is really weird is that a Windows Store app that we wrote to test this registers and receives notifications using the same credentials without any issue. Can anyone point me in the right direction on this? The error messages above aren't very helpful.
It turns out that the test devices all had the automatic date and time synchronization turned off. The iPad I was primarily testing with was only off by about 20 or 30 seconds, so I didn't notice it was off. Another question involving the same thing with a Windows or Windows Phone registration clued me into it, but I can't find the link to it now. Apologies for that, thanks to whoever that was!
Looking at the API, it makes sense why it's so sensitive to this. It uses the date and time to generate the SAS Token, thus the unauthorized response when the time is just a few seconds off.
We are connecting to 'gateway.push.apple.com 2195' from a c# console with a right device token and production certificate. Ssl authentication went fine and no issues reported but the device doesn't recieve any alert message or badge. Device is registered to recieve notifications. [Settings->Notifications is set to ON for badge, alert and sound]. We are using apns-sharp-1.0.3.0 c# source code. what else could go wrong and how to debug the issue.
P.S Note: One thing we noticed, the call back routine (OnAsyncRead.IsCompleted) hasn't been completed and we have to Dispose() it forcibly. Desperately looking out for a solution, anyone's feedback would be of great help. Thank you.
small time fix only - sleep the thread before closing and disposing - giving time for the APN to be sent.