evollu / evollu/react-native-fcm
Upgrading app version number results in a refreshed FCM token that does not work
- Dominant language
- Java
- Stars
- 1.7k
- Forks
- 661
- PR merge metrics
- No merged PRs in 30d
Description
To begin with, my app is working fine and notifications are received in foreground, background and killed states.
Changing the code and restaring, including upgrading the build number causes no change in behaviour. Let's say that the FCM token the app receives is Token A. The token value remains constant while I make changes to the app.
Upgrading the *version number* of the app, e.g. from 2.4.1 to 2.4.2 causes a big problem in the app: When the app asks for the FCM token, the app now receives Token B. There is a change in the token. Normally, I would say that this is OK, just inform the backend of the new token. But the new token does not work.
Sending push notifications to the app using Token B has no effect in the app.
Sending push notifications to the app using Token A works fine like before.
React Native version: 0.57.8
react-native-fcm version: 16.1.0
iPhone 7 Plus running iOS 12.1.4.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by reproducing the version upgrade on the stated iPhone and comparing the refreshed FCM token with the previous token; done means notifications sent to the refreshed token are received.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase, ios, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100