Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(@capacitor/push-notifications): Add common issue about iOS simulator support and device tokens #2026

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions push-notifications/README.md
Expand Up @@ -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 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)

---

## Example
Expand Down