diff --git a/push-notifications/README.md b/push-notifications/README.md
index 85fca33b1..7702324cd 100644
--- a/push-notifications/README.md
+++ b/push-notifications/README.md
@@ -136,6 +136,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