Apptentive registration on Worker thread causing ANR

[dbharani]

We can still see that ANR with some devices (eg: Samsung Galaxy J7 Prime, 8.1 OS). Find the stacktrace below:

at android.os.BinderProxy.transactNative (Native method) at android.os.BinderProxy.transact (Binder.java:777) at android.security.IKeystoreService$Stub$Proxy.exist (IKeystoreService.java:846) at android.security.KeyStore.contains (KeyStore.java:527) at android.security.keystore.AndroidKeyStoreSpi.engineContainsAlias (AndroidKeyStoreSpi.java:951) at java.security.KeyStoreSpi.engineGetEntry (KeyStoreSpi.java:493) at java.security.KeyStore.getEntry (KeyStore.java:1621) at com.apptentive.android.sdk.encryption.resolvers.KeyResolver23.loadExistingKey (KeyResolver23.java:59) at com.apptentive.android.sdk.encryption.resolvers.KeyResolver23.resolveSecretKey (KeyResolver23.java:44) at com.apptentive.android.sdk.encryption.resolvers.KeyResolver23.resolveKey (KeyResolver23.java:39) at com.apptentive.android.sdk.encryption.SecurityManager.resolveMasterKey (SecurityManager.java:106) at com.apptentive.android.sdk.encryption.SecurityManager.getEncryption (SecurityManager.java:61) at com.apptentive.android.sdk.ApptentiveInternal.<init> (ApptentiveInternal.java:170) at com.apptentive.android.sdk.ApptentiveInternal.createInstance (ApptentiveInternal.java:237) locked <0x0ac7d295> (a java.lang.Class<com.apptentive.android.sdk.ApptentiveInternal>) at com.apptentive.android.sdk.Apptentive.register (Apptentive.java:129) at com.apptentive.android.sdk.Apptentive.register (Apptentive.java:111)