-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fatal Exception: kotlinx.serialization.json.internal.JsonDecodingException: Unexpected JSON token at offset 0: Expected start of the object #142
Comments
@beinghassandar1 Do you mind checking if you're using the right endpoint/config ?
|
We are using our self hosted api endpoint. 99% of the users get correct data... Few users are getting Json from the same endpoint. |
Hi, @beinghassandar1. We will check that and get back to you asap. |
Thank you. Just fyi, we are seeing more crash reports for other Android versions too. Like Android 9, 11, 12, 13, 14. |
Thank you for the detailed information. It will help us fix that. |
But what actually highlights that 1 percent with not right information. Maybe some version or some properties? |
Hhmm, hard to say. They are all on the latest build as we have recently released the new version with Growthbook sdk implementation. |
We are also getting more reports now but the crash is always something to do with wrong json.
|
@beinghassandar1 Is there a pattern you see on these crash errors? the 1% users are consistently getting this error? if it consistent, is there a way for you to replicate this error? |
Hi, @beinghassandar1 . After what steps did these users receive that, and what options did the user enable? |
Hey, When user logins and we initialize the sdk, we see a crash from there users. Also, I got a new crash log. ourserver_url = the url of our own hosting server
|
Hi, @beinghassandar1. Thank you for information, we will check that. |
Hey guys, we are getting this crash on Android 13.
Can you guys please tell us why growth book is trying to deserialize
<!DOCTYPE html><html lang="pt"
from the backend instead of the actual json for features?Lib Versions:
Initialization
The text was updated successfully, but these errors were encountered: