From 7b22e18a91ac047d8b9cfa2735a82f1444ba4aaa Mon Sep 17 00:00:00 2001 From: Matthew Balshaw Date: Wed, 7 Feb 2024 10:32:52 +0100 Subject: [PATCH 1/2] Update README.md Added a section to common issues, reminding users that on an iOS simulator the register event will fail silently. --- push-notifications/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/push-notifications/README.md b/push-notifications/README.md index 22d5fe7dd..cde60c7c0 100644 --- a/push-notifications/README.md +++ b/push-notifications/README.md @@ -130,6 +130,8 @@ On Android, there are various system and app states that can affect the delivery * If the device has entered [Doze](https://developer.android.com/training/monitoring-device-state/doze-standby) mode, your application may have restricted capabilities. To increase the chance of your notification being received, consider using [FCM high priority messages](https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message). * There are differences in behavior between development and production. Try testing your app outside of being launched by Android Studio. Read more [here](https://stackoverflow.com/a/50238790/1351469). +On an iOS simulator, there is no way to receive the registration event, or a registrationError event in the listeners. It will fail silently. You can grant the permissions for push notifications in a simulator, but in order to test registering the device token you will need a physical device. + --- ## Example From 556a67e4fc361e63f36eb8dbdcb269f614383aca Mon Sep 17 00:00:00 2001 From: Matthew Balshaw Date: Wed, 7 Feb 2024 11:13:25 +0100 Subject: [PATCH 2/2] Update README.md Added caveat that it works with macOS 13+ and xcode 14+ --- push-notifications/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/push-notifications/README.md b/push-notifications/README.md index cde60c7c0..d9992148a 100644 --- a/push-notifications/README.md +++ b/push-notifications/README.md @@ -130,7 +130,7 @@ On Android, there are various system and app states that can affect the delivery * If the device has entered [Doze](https://developer.android.com/training/monitoring-device-state/doze-standby) mode, your application may have restricted capabilities. To increase the chance of your notification being received, consider using [FCM high priority messages](https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message). * There are differences in behavior between development and production. Try testing your app outside of being launched by Android Studio. Read more [here](https://stackoverflow.com/a/50238790/1351469). -On an iOS simulator, there is no way to receive the registration event, or a registrationError event in the listeners. It will fail silently. You can grant the permissions for push notifications in a simulator, but in order to test registering the device token you will need a physical device. +On an iOS simulator before macOS 13 and Xcode 14, there is no way to receive the registration event, or a registrationError event in the listeners. It will fail silently. You can grant the permissions for push notifications in a simulator, but in order to test registering the device token you will need to upgrade to at least macOS 13 and Xcode 14, or use a physical device. [Release notes](https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes#Simulator) ---