I've an apps with push notification working well on it. After i upgrade device to iOS8, i unable to receive push notification on my device, even with correct device token, taken with function didRegisterForRemoteNotificationsWithDeviceToken .
The push notification is working perfectly on iOS < 8.
i do add a function didRegisterUserNotificationSettings for compatible with iOS8. I able to get prompted request permission for push notification dialog, and able to get device token string. Sadly, i still get no luck in this.
Any help?
Take a look here
https://support.pagerduty.com/hc/en-us/articles/203238050-Receiving-push-notifications-on-iOS-8
I have the same issue too
read this : As of September 19, 2014, our engineers confirmed with Apple that this is a known issue with the iOS 8 upgrade.
Khodor
You should see and read session number 713 of Apple #WWDC2014.
It has got all the information regarding the IOS8 Push Notification actions.
Here is a link for this. Watch "What's new in ios notifications" videos :
https://developer.apple.com/videos/wwdc/2014/
Related
I'm wondering if there's a known bug in WatchOS 6.1.1 regarding local notifications triggered from the watch?
I have an app that I developed about two years ago on watchOS 4. It would send local notifications from the watch during background processing. It worked great. The code sat for about two years and I was asked to update it. Since updating, I cannot get local notifications from my watch to work when I distribute builds through TestFlight. When I run the app through Xcode it works (both with the Debug and Release schemes). I saved logs in the watch app that show that the UNUserNotifications.current.add() does not pass an error into its completion handler. I can get local notifications from the handset in TestFlight builds to work and I can mirror those on the watch. But I cannot get local watch notifications to work. Does anyone have any idea why this might be? Is there a known bug? Have local watch notifications changed in a breaking way since watchOS 4?
I've found my issue. I think it's a new bug in watchOS6. It seems that permissions aren't being properly communicated from the handset to the watch. After giving permission for notifications on the handset, I would check for notification permissions on the watch and get .notDetermined. Strangely, if I downloaded the handset app and quickly gave notification permissions BEFORE the watch app had finished downloading, then it properly received notification permissions. I fixed this by simply requesting notification permissions on both the handset and the watch.
I have configured the Appceter Xamarin.ios for sending notifications to iOS devices. I entered everything as is mentioned in AppCenter but when I send notifications, it says Sending and looks like its stuck there. I don't know what the issue can be. Any ideas here?
As you can read here, push notifications cannot be tested on a simulator for iOS. You will need to test it on a device
Because of configuration requirements for iOS push notifications, you
must deploy and test the sample application on a physical iOS device
(iPhone or iPad) instead of in the simulator.
I am currently running iOS 10 beta 8 with Xcode 8.0 beta 6 and the custom sound does not play when I receive a push notification with the correct payload.
I have verified the payload and it is in the correct format per the apple documentation:
{
"aps" : {
"alert" : "You got your emails.",
"badge" : 9,
"sound" : "bingbong.aiff"
},
"acme1" : "bar",
"acme2" : 42
}
When I send the same payload to the same build on iOS9 the custom sound plays properly.
Does anyone know if there are any other changes in iOS 10 that I need to make?
This problem seems to only affect apps installed via Xcode. The issue persists even if you later update the app from a different source.
The solution is to completely remove the app, and reinstall it from TestFlight or the App Store.
In effect, this bug should not affect your end users.
Edit 2016-10-15:
Unfortunately it seems that I was mistaken. This appears to be a bug on iOS 10 that can, in fact, affect App Store apps also. If it is of any consolation, apps such as Facebook and WhatsApp are affected too. The solution is apparently to force restart your phone, but unfortunately there doesn't seem to be much we can do about it as developers.
Apple Fixed Issue:
Based on this comment, Apple has seemed to fix the issue in iOS 10.2
Try installing your app using Test Flight and after implementing initial process to update device token just restart your device.
You'll get what you have been looking for.
Credit goes to - binncheol
Having our user restart their device is correcting the issue for us.
This is an issue for us regardless of how the app was installed (TestFlight or from the app store).
There is definitely an iOS10 bug which still persists as of 10.0.2. It affects many apps including popular ones such as Whatsapp and Messenger. The workaround is just to power cycle the device, after which point the notification sounds are correct. It doesn't seem to matter how the app is installed.
I can't find any documentation of this from Apple (go figure) but there is more info here: http://thetechbeard.com/how-to-fix-notification-sound-problem-in-ios-10/.
As reported here lots of other people are having this problem. Hopefully Apple fixes it soon.
I uninstalled the app, turned off the real device, reinstall the app, and then the custom notification sound started working. It didn't work before I restarted my device XD
I am testing an app on iOS 9 (13A340) on iPhone 6, mainly the remote notification part. The remote push notification generated from AWS SNS cannot be received by the app, though the same app on iOS 8 works as expected. Is this due to the beta version of the iOS 9 or?
Thanks for any tip.
/Leonard
I have tried remaking the APSN development certificate and etc. and then it starts working, although I don't know what problem really was.
This didReceiveRemoteNotification method may also be called if a “silent/background” notification is received. As such, you should also enable “Background Modes: Remote Notifications” in the target capabilities panel (or else you’ll see warnings in the console).
Read more: http://www.intertech.com/Blog/push-notifications-tutorial-for-ios-9/#ixzz3tH8pRbz0
check image description here
I am using Xamarin.Forms.Labs to send SMS messages from my app. It works great on WP and Android but with the iOS it opens up the default texting screen and allows you to send a text but then I am unable to get back to my app. I click cancel or the iPhone button and reopen my app and it is still on the texting screen. Any ideas what I could be doing wrong or why it doesn't return to my app once I have finished texting? Is anyone else having this issue?
This was a bug in the iOS implementation. I just pushed a fix for it and you can use the latest code (master branch) to test it out.
https://github.com/XLabs/Xamarin-Forms-Labs/pull/498
I will get it included in the next release package.