slawomir.budzynski
slawomir.budzynski
Hey @abora97 have you found a solution?
@jena-chakour Yes, I always kept the value of the previous email in a function to retrieve the token needed for the `disableDevice` query. Currently, we are using the default JWT...
Below you can find the whole crashlog from BugSnag from the production: ``` java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$4.done(AsyncTask.java:399) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383) at java.util.concurrent.FutureTask.setException(FutureTask.java:252) at java.util.concurrent.FutureTask.run(FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:289)...
If it's about a device, it can be reproduced on every Android phone, we detected it also on OS version from Android 10 to 14. Personally I'm using for tests...
In our case it looks that this helps (no crash and lib can continue fetching new JWT token and sending events): 
Maybe it's related with this issue: https://github.com/Iterable/iterable-android-sdk/issues/741
@lposen It was caused by the incorrect version of the Android Iterable SDK, resulting from the our patch and the version wildcard "*" inside the patch. There was a breaking...