Problem with IOS token
See original GitHub issueHi, I’m perfect with Android, but with IOS I don’t know why when I try to send a notification using the token generated, it says invalid token
in Firebase Cloud Messaging. What could be wrong?
I’m working with RN 0.26.2 and RNPN 1.0.7
Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:12
Top Results From Across the Web
iOS-13 Unable to receive Device Token. - Apple Developer
After upgrade to iOS-13, we are unable to receive Device Token (intermittent) when we perform UIApplication.shared.registerForRemoteNotifications().
Read more >The Trouble with Using iOS Device Tokens - Airship Support
The main problem with device tokens is that they can change and become an unreliable method for addressing notification delivery causing issues with:...
Read more >iOS: Invalid token error for push notifications
The most likely cause is that the notification was sent via the wrong gateway due to a misconfiguration, but may also be caused...
Read more >iOS 14: UC Mobile Token issues & errors after Update
Common iOS 14 UC Mobile Token issues · UC Mobile Token always crashes · UC Mobile Token not loading · UC Mobile Token...
Read more >Token import fails after upgrading to the SecurID Token ...
RSA Version/Condition: 3.0. Platform: iOS 14.6. Issue. Issue. Token import fails with an error: "Error Occurred Token import unsuccessful.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @mohamed-alashry @damathryx! sorry for the delay in the response. Now I’m using react-native-fcm
@theohdv thanks, i just went with agrass solution use react-native-fcm and im getting the correct token now.