-
Notifications
You must be signed in to change notification settings - Fork 368
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
does not recognize the device in the dashboard when install the signed apk in device. #547
Comments
@amir-m7 For issues where the device doesn't register with OneSignal, that will generally display an error in logcat. Can you please copy + paste your logcat for at least 10 seconds after opening your app? |
@Nightsd01
|
@amir-m7 unfortunately that doesn’t really help. Can you set the OneSignal log level to |
@Nightsd01 |
@amir-m7 You will need to call |
@amir-m7 This is a bit confusing. Are you saying your app is crashing? Unfortunately, your test app includes If you're getting a crash, it's related to this, which wouldn't be related to our SDK:
|
@Nightsd01 my app name is notification.my app is not crashing.in debugging recognize my device in dashboard.when generate the signed apk and install it does not recognize in dashboard. |
When you say the device is "not recognized", what do you mean? You mean that the device is not getting registered at all and doesn't show up in the dashboard? When I look in your logs, I do see this:
That means that the device has a OneSignal User ID, which means it registered successfully. Since the device is getting registered with OneSignal, that means it should definitely show up in the dashboard. |
@Nightsd01 |
Hi, I'm facing this issue too, both on ios and android, where sometimes the device gets listed in the dashboard and sometimes not, plus when teh device gets registered the tags are not send most of the time, i call sendTags but again I can't see the tags being send in the dashboard. I called Couldn't get more info out of that. Edit: Seems like this is related with react-native-navigation #516 |
This does seem to be an incompatibility issue with the react-native-navigation dependency. Please do try using native initialization and let me know how it goes. |
@Nightsd01 |
I can't seem to get it working, native initialization didn't help and I can't find any logs about it |
@amir-m7 @phantom1299 Can you please copy + paste your In the The installation instructions for |
I'm returning the package:
|
|
@amir-m7 Yeah, I have created a project using Would it be possible for you to upload a sample project that reproduces this issue? If you want to send us your full project that works as well, but don't post it publicly, contact OneSignal support (on our dashboard website click the ? button) and link them to this git issue. |
@Nightsd01 |
@amir-m7 I am not sure what you mean....? I was asking you to send us an example project where you are able to reproduce this issue |
@Nightsd01 |
The particular issue that caused this problem in Amir-M7's case should now be resolved in 3.2.5. If anyone else encounters this issue going forward, please comment here and I'll be happy to help investigate. |
Description:
When i generate signed apk and install on device , it does not recognize the device in the dashboard. But in debugger environment, recognizes the device and show in dashboard and it's not a problem.
Environment
The text was updated successfully, but these errors were encountered: