New issue
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
Google Play Services Library Error #525
Comments
@DaniloCouto This is definitely an android support library version issue. Can you post your |
@DaniloCouto check the new version 3.2.4, they fix it. |
@adirzoari , Still happens on 3.2.4, with the same errors on Adb logcat and on Onesignal User Dashboard.
@Nightsd01 Sure thing, here it is:
Edit 1:
Of course, I've clean the android project with |
@DaniloCouto Are you just using the react-native-onesignal Can you also post your |
@Nightsd01 I've created a new react-native project and added the react-native-onesignal package through Yarn. Here it is:
Edit 1:
Edit 2: |
Same problem here , @DaniloCouto you fix it??? |
I got the same problem.. @DaniloCouto did you manage to fix it? I searched about it everywhere and still no works :( |
@ifanfaizal, @lahed Sorry to hear that, but i'm here to find a solution too...
|
Danilo, you are supposed to insert |
@brunoandradebr Well observed my fellow countryman. |
Added this to dependence after install Google Play Service from android studio sdk manager, and somehow worked, but the app crashed, then I refreshed onesignal user list and the error keep persisting =[ |
I think it's working now! I'v installed Google Play Service from Android Studio, It's not supposed to insert any line, you need to close bundle and compile again. It's showing subscribed with a check icon! I don't even inserted onesignal extra lines, it's the same way react native has created. |
@brunoandradebr @DaniloCouto @ifanfaizal I fix, i change sdkVersion and version appcompat Changes:
In dependencies My build.gradle (android)
In cmd: cd android && gradlew clean Uninstall app from my AVD and compile with react-native |
@lahed Aaahhh it's working bro!! 💃 thank you very much for your solution.. I spent 3 days to make it work but no results at all.. and today, you just save my life 😃 |
@lahed , works like a charms, thx. |
@lahed ty, its work |
i have 2 project using one signal |
@stevanus1997 maybe u already defined the init on the build.gradle in project 2 (?) (in other words, u defined OneSignal init with an older way) so u didn't need to init again in App.js |
project 1
project 2
@ifanfaizal thats my build.gradle |
@lahed thank you so much. Now its working like charm...!!! |
I followed @lahed's solution but I still get the same error from OneSignal's dashboard ... could someone show me his fixed |
Try close compiler and recompile again. |
Done that multiple times already 😕 |
Have you installed Google Play Service with Android Studio ? |
Yup, the latest version of it, I'm running on Android 8.0 |
|
Inside one signal list, remove actual device Option > Delete, uninstall debug app then compile again. |
+1 not receive onIds with init call from react native js |
@congnguyen91 That is expected. The If you want to force |
Hi @lahed, am I seeing your proposed changes right #525 (comment), the min. required Does this mean Android 6.x is not supported anymore, because my current Thanks for your help! |
@natterstefan I'm almost certainly not. The one that defines the lower devices is minSdkVersion, so, everything should work perfectly, unless a native API is not supported. I tested on Android 4.4 and it works fine |
I solved here.... |
We have updated our documentation to include making sure This is one of the things @lahed suggested in #525 (comment). The other new part is adding the OneSignal Gradle plugin to your project. With this you won't have to manually update Make sure you have follow the new |
@lahed thank you so much, I've tried to figure out this issue for 2 days, and finally found a very helpful one here, thank you. |
I had the same, but got it working by calling onesignal.configure() like this: OneSignal.init("my-onesignal-id"); This was with: followed the onesignal documentation to the bell and had other info: |
In my case, I never got any errors on the OneSignal dashboard; the device was getting registered with OneSignal fine. The Adding this right after OneSignal.init() fixed my issue:
Hope this helps others. |
Same issue here package.json:
android/build.gradle
android/app/build.gradle
src/main/AndroidManifest.xml
src/debug/AndroidManifest.xml
|
Hello @lahed The required sdk version is 31. Does the same fix still apply?? |
Description:
The registred device returns an error on OneSignal dashboard, therefore unable to receive push notifications.
Environment
package.json
Steps to Reproduce Issue:
compile project(':react-native-onesignal')
on dependencies. It can't compile without that dependence.on Ids listener , erase the class method and create a local one, so we can see the id.
If we didn't do it, the id would never return
On Init insert your app ID.
10. then : react-native run-android.
(On adb logcat it will return an error, but you will se the id on debug mode.)
11. Search the id on OneSignal Dashboard and there it is.
Anything else:
Edit 1:
I've tried to do those, but without success:
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE"/>
to the AndroidManifest.xmlThe text was updated successfully, but these errors were encountered: