Skip to content
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

[Bug]: Erroneous "Usage Duration" for Android subscriptions in SDK 5.2.0 #1715

Open
2 of 3 tasks
mikemonaco opened this issue Jun 17, 2024 · 5 comments
Open
2 of 3 tasks

Comments

@mikemonaco
Copy link

mikemonaco commented Jun 17, 2024

What happened?

When using react-native-onesignal SDK 5.2.0 (and possibly other 5.X.X version), the OneSignal dashboard is reporting a usage duration of "100000000" seconds by default for Android subscriptions. Usage duration seems to accrue normally from there (ie. 100000065, after 65 seconds of usage). This issue does not appear to be happening on iOS.

Steps to reproduce?

1. Install and configure react-native-onesignal SDK 5.2.0
2. Run react native app on Android
3. Login to https://dashboard.onesignal.com/login
4. Select your app
5. Navigate to Audience > Subscriptions
6. Observe value in "Usage Duration", you may need to launch and close the app a few times, or wait a few minutes for this value to populate.

What did you expect to happen?

I expect the usage duration to start accuring from 0 seconds instead of 100000000 seconds.

React Native OneSignal SDK version

5.2.0

Which platform(s) are affected?

  • iOS
  • Android

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@mikemonaco
Copy link
Author

Below is a screenshot showing this issue:

Screenshot 2024-06-17 at 1 12 26 PM

@rgomezp
Copy link
Contributor

rgomezp commented Aug 12, 2024

Howdy Mike,
Thanks for your patience. This is reproducible and we are investigating.

@mikemonaco
Copy link
Author

@rgomezp wanted to check in on the status of this, thanks.

@mikemonaco
Copy link
Author

@rgomezp just checking in, is this fixed?

@rgomezp
Copy link
Contributor

rgomezp commented Oct 22, 2024

Hey Mike,
Not yet. I apologize for the inconvenience.

@jinliu9508 is this something you can take a look at soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants