Sammekl

Hi, Just change your dependency to the following: ``` dependencies { implementation('com.twitter.sdk.android:twitter:3.3.0@aar') { transitive = true } } ```

I have created a PR which resolves this issue: https://github.com/twitter/twitter-kit-android/pull/131 To reproduce you can use `context.getApplicationContext()` instead of `context` when creating the intent. This mimics the same behaviour as reactContext....

@efrohnhoefer Any progress on this? As I've said, we have a lot of users affected by this bug.

I've introduced a workaround in my Application onCreate() method: For Kotlin: `Thread { TweetUi.getInstance()}.start()` For Java: `new Thread(TweetUi::getInstance).start();` This will make sure that the TweetUi is loaded on app start

This PR is not necessary when https://github.com/anitaa1990/Biometric-Auth-Sample/pull/9 gets merged, which I prefer due to additional functionality

Could you post the nested exception thrown from: **Caused by: java.lang.RuntimeException: Failed to init Cipher**? It should be one of the following: ```CertificateException | UnrecoverableKeyException | IOException | NoSuchAlgorithmException |...

There's no solution for this currently. It's against material design to do such a thing, but if you really need something like this, a quick workaround would be to override...