Hi,
I have recently noticed that after migrating from SDK to version 3.5.6 and 3.5.11 the following ANR started to happen more frequently whenever we attempt to initialise the SDK.
The ANR is affecting lots of our users with Android 12 (98%) and several device brands.
Also, the ANR rate increase around 50% when starting the latest version 3.5.6.
The initialise is done upon application startup following the documentation instructions as stated here
Here is the stack trace:
main (timed waiting):tid=1 systid=16634
at java.lang.Thread.sleep(Native method)
at java.lang.Thread.sleep(Thread.java:450)
at java.lang.Thread.sleep(Thread.java:355)
at android.security.KeyStoreSecurityLevel.interruptedPreservingSleep(KeyStoreSecurityLevel.java:206)
at android.security.KeyStoreSecurityLevel.createOperation(KeyStoreSecurityLevel.java:115)
at android.security.keystore2.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:334)
at android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:234)
at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2999)
at javax.crypto.Cipher.tryCombinations(Cipher.java:2910)
at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2815)
at javax.crypto.Cipher.chooseProvider(Cipher.java:792)
at javax.crypto.Cipher.init(Cipher.java:1307)
at javax.crypto.Cipher.init(Cipher.java:1242)
at com.iterable.iterableapi.IterableDataEncryptor.decryptModern(IterableDataEncryptor.kt:216)
at com.iterable.iterableapi.IterableDataEncryptor.decrypt(IterableDataEncryptor.kt:171)
at com.iterable.iterableapi.IterableKeychain.secureGet(IterableKeychain.kt:78)
at com.iterable.iterableapi.IterableKeychain.getEmail(IterableKeychain.kt:91)
at com.iterable.iterableapi.IterableApi.retrieveEmailAndUserId(IterableApi.java:449)
at com.iterable.iterableapi.IterableApi.initialize(IterableApi.java:598)
...
at androidx.startup.AppInitializer.doInitialize(AppInitializer.java:180)
at androidx.startup.AppInitializer.doInitialize(AppInitializer.java:173)
at androidx.startup.AppInitializer.doInitialize(AppInitializer.java:173)
at androidx.startup.AppInitializer.doInitialize(AppInitializer.java:138)
at androidx.startup.AppInitializer.initializeComponent(AppInitializer.java:117)
...
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1213)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6915)
at android.app.ActivityThread.access$1600(ActivityThread.java:261)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2154)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loopOnce(Looper.java:238)
at android.os.Looper.loop(Looper.java:357)
at android.app.ActivityThread.main(ActivityThread.java:8098)
at java.lang.reflect.Method.invoke(Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1026)
Can someone please help me out with this issue?
Hi,
I have recently noticed that after migrating from SDK to version 3.5.6 and 3.5.11 the following ANR started to happen more frequently whenever we attempt to initialise the SDK.
The ANR is affecting lots of our users with Android 12 (98%) and several device brands.
Also, the ANR rate increase around 50% when starting the latest version 3.5.6.
The initialise is done upon application startup following the documentation instructions as stated here
Here is the stack trace:
Can someone please help me out with this issue?