question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Remote token not registered

See original GitHub issue

Unfortunately, I am facing an issue after “upgrading” from master to 3.3.1. I am using the provided example and added the google-services.json from firebase to android/app as well as replacing the react-native-push-notification version in package.json with “3.3.1”. Then I ran npm install and started the app, nothing was logged and no register token is shown.

package.json dependencies:

  "dependencies": {
    "@react-native-community/push-notification-ios": "^1.1.1",
    "react": "16.11.0",
    "react-native": "0.62.2",
    "react-native-push-notification": "3.3.1"
  },

I saw that implementation 'com.google.firebase:firebase-analytics:17.3.0' was missing in android/app/build.gradle. So, I added it. But still the same, the app is not registered with firebase.

Otherwise nothing was changed in the original example. I retrieved it by using:

git clone https://github.com/zo0r/react-native-push-notification.git
git checkout tags/3.3.1

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:42 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
Dallas62commented, May 4, 2020

Hi @daudhumayun A fix will not be available in your time range. For debug purpose, you can install the version on master (yarn install + repository url) For your release, I suggest you to revert to the latest working for you. I’m not able to reproduce it, so I need to know if this work on example project for someone or not. Else, provide AndroidManfest or more.

0reactions
Dallas62commented, Mar 17, 2021

So it’s probably an issue on your configuration, I recommend you to double check if it’s the same project. If still not working, StackoverFlow should be more appropriated since you have a token generated from the app.

Read more comments on GitHub >

github_iconTop Results From Across the Web

ios - Device Token not received when registering for remote ...
I somehow can not receive the device token when registering for remote notifications. I get the modal saying "Do you want to allow...
Read more >
Error: 'Invalid authentication token or client is not registered ...
When launching the Backup Manager remotely, the following error appears: 'Invalid authentication token or client is not registered'.
Read more >
Registering Your App with APNs - Apple Developer
Register your app with APNs and receive a globally unique device token, which is effectively the address of your app on the current...
Read more >
Best practices for FCM registration token management
On this page · Basic best practices. Retrieve and store registration tokens; Detect invalid token responses from the FCM backend · Ensuring registration...
Read more >
Creating a secure registration token
This guide is for users who want to administer BigFix® Remote Control. Configuration and troubleshooting options in the Admin menu · Creating a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found