We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi @jefflinwood
While initializing the client, it crashes with
java.lang.NullPointerException: accessToken must not be null
The logs show
The order seems to be
execute
This causes a crash as register() is called in step 2, before step 3 is ran, causing mAccessToken to be null.
register()
mAccessToken
null
I'm not too sure why the FCM token is retrieved so quickly, perhaps because I am also using capacitor-push-notifications, which uses the same library.
Does moving FCM token retrieval into the execute method make sense?
The text was updated successfully, but these errors were encountered:
This was caused by using a wrong version of firebase messaging.
Closed
Sorry, something went wrong.
No branches or pull requests
Hi @jefflinwood
While initializing the client, it crashes with
java.lang.NullPointerException: accessToken must not be null
The logs show
![Screenshot 2022-01-05 at 2 18 09 AM](https://user-images.githubusercontent.com/7776614/148105234-3f5e34a0-8724-469e-9d3d-10f6ff7cc0b9.png)
The order seems to be
execute
methodThis causes a crash as
register()
is called in step 2, before step 3 is ran, causingmAccessToken
to benull
.I'm not too sure why the FCM token is retrieved so quickly, perhaps because I am also using capacitor-push-notifications, which uses the same library.
Does moving FCM token retrieval into the
execute
method make sense?The text was updated successfully, but these errors were encountered: