App crashes when JWT token expired before it retried to refresh it on init

[buuuudzik]

We are using the Iterable SDK in our project, currently at version 1.3.19: "@iterable/react-native-sdk": "1.3.19",

Recently, we have encountered errors in production, which I have also been able to reproduce in development mode. It appears that if the app is left logged in and then fully closed for a period longer than the JWT token expiration time, the Iterable SDK does not attempt to refresh the token before using it. This results in a complete app crash, and we have no means to prevent it.

Could you ensure that your SDK cannot cause the app to crash entirely? There should be an error handler to allow us to check what happened in the SDK without encountering an unmanageable low-level error.

Additionally, it would be helpful if we could pass a new auth token via Iterable.setEmail(email, token) while still utilizing the auto-refresh mechanism. Currently, when we pass the token using the mentioned method, the auto-refresh mechanism stops working.

Here is the error we found that causes the app to crash completely:

[jena-chakour]

Hi @buuuudzik, thanks for sharing -- I've reached out through your Support ticket for additional details; please share the full crash log and device info. We will look into this :)

[buuuudzik]

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)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:929)

Caused by: java.lang.AbstractMethodError: abstract method "void com.iterable.iterableapi.IterableAuthHandler.onAuthFailure(com.iterable.iterableapi.AuthFailure)"
        at com.iterable.iterableapi.IterableAuthManager.handleAuthFailure(IterableAuthManager.java:176)
        at com.iterable.iterableapi.IterableRequestTask.executeApiRequest(IterableRequestTask.java:193)
        at com.iterable.iterableapi.IterableRequestTask.doInBackground(IterableRequestTask.java:61)
        at com.iterable.iterableapi.IterableRequestTask.doInBackground(IterableRequestTask.java:34)
        at android.os.AsyncTask$3.call(AsyncTask.java:378)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:289)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:929)

[buuuudzik]

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 Samsung Note 10 Plus.

[buuuudzik]

In our case it looks that this helps (no crash and lib can continue fetching new JWT token and sending events):

[buuuudzik]

Maybe it's related with this issue: https://github.com/Iterable/iterable-android-sdk/issues/741

[lposen]

Hi all. Can you confirm whether or not this is still an issue?

[buuuudzik]

@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 change between the Android Iterable SDK versions.

But what still appears is some race condition in the authToken refreshing mechanism. Please ensure that the register or unregister won't trigger before the up-to-date token is successfully fetched, or will be retried if the register/unregister call fails.

[lposen]

@buuuudzik Have you patched the Iterable RN SDK with a newer version of the Android SDK, by any chance?

The Iterable RN SDK hasn't incorporated newer versions of the Iterable Android SDK, so there will likely be several breaking issues if you have patched it with a newer version. The way that token refreshes are handled changed quite substantially in the newer versions of the Iterable Android SDK.

We are currently working on bringing the RN SDK up to speed with the newer Android and iOS versions.

[lposen]

FYI for anyone watching this thread -- JWT is currently in development, and we plan on releasing it before the end of Q4.

[buuuudzik]

Thanks @lposen