React-native-onesignal: Warning com.onesignal.PushRegistratorFCM->getApiKey

[MayoudP]

Description:

Hello, currently having the same warning mentioned in the issue below. Is an update planned in the next coming days to fixed it for react-native ?
This is a warning, I'm getting when trying to submit a new version for the Android Store...
https://github.com/OneSignal/OneSignal-Unity-SDK/issues/278#issue-575259072

Environment

"react": "16.8.6", "react-native": "0.60.5", "react-native-onesignal": "^3.6.5",

Steps to Reproduce Issue:

1. Try to submit update on android console application. Getting a warning.
   

[Jacklol]

same problem

[yaronlevi]

This issue has been fixed in the Android SDK. It will be great if we can get an update to the RN SDK to include this update.

[quynhapl]

This issue has been fixed in the Android SDK. It will be great if we can get an update to the RN SDK to include this update.

I am waiting for Flutter SDK, too!

[maxencehenneron]

Looks like we need to bump the one signal SDK from 3.12.7 to 3.13.0. I wonder if the upgrade is straight forward.

Looking at the release notes

Set and remove external user id now have completion callback
Callback for completion added to verify the status of the set or remove of an external user id (push & email)

we may have to refactor setExternalUserId to fix this issue.

[achmadfaturrizky]

I have the same problem, I hope it will be fixed immediately

[ermankuruoglu]

I also have same problem

[jkasten2]

@maxencehenneron The external user id callbacks are optional.

If you need to bump the OneSignal-Android-SDK native update version now edit this update it in react-native-onesignal's android/build.gradle file. Using 3.13.0 will give you the version where this warning is fixed.

However this warning is a false positive, you can safely release an update to your app without updating.

We are looking to release a react-native-onesignal update sometime next week. It will include the the set external user id callback which is why we haven't simply released an update with just the version bump.

[mrkindy]

Hello @jkasten2, we are waiting your release

[jkasten2]

This fixed is now included in the 3.7.1 release.
https://github.com/OneSignal/react-native-onesignal/releases