My iOS app receives a push notification. Then the app is closed and runs in the background. After reopening the app, the push notification is received again. Only when the app is completely closed does the push notification no longer occur. Why? How can you prevent this?
Related
I'm currently trying to add firebase push notifications to iOS unity project in xcode, but nothing seems to work. Everything else works perfectly, and there is no problems with push notifications in the same project on android. No push notifications in testlight or in the released version from AppStore. Also the permission for using notification do not show up after launching.
PS I am not a developer, just a QA-engineer being asked to manage all the problems with iOS)
added push notifications capability
added remote notification capability
uploaded app APNs to firebase account
enabled push notifications in provisioning profile
added user notification usage description to info.plist
Nothing seems to work. I saw post about adding "registerForRemoteNotifications" string in AppDelegate but I can't find it in our project.
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'm running into an issue with push notifications using Nativescript and Onesignal
Onesignal keeps telling me the app is missing push notifications in xcode.
But when I run the app, I do get the 'appname would like to send you notifications' message and under xcode everything seems to be set correctly.
I tried deleting the platforms folder, rebuilding the app and so on, but it remains the same message. When I change the app version, I do see the app version change on the onesignal platform, so the informations is passing but apparently apple does not let the notifications through.
Anyway to debug this? How can I be sure the app has push capabilities?
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.