Closed mchemin closed 3 years ago
Hi @mchemin sorry to hear you're having an issue with the SDK.
I tried to reproduce this in one of our internal apps (Adding "androidx.lifecycle:lifecycle-livedata-ktx:2.3.0"
), but I wasn't able to recreate the issue. Do you have more information, or a reproduction sample for us to debug?
I'm sorry it was with androidx.lifecycle:lifecycle-runtime-ktx:2.3.0
I'll try to make a sample before tomorrow.
Thanks for the update! I'm able to reproduce now.
I've created an internal issue for us to fix this: OKTA-383062
As a temporary workaround, I'd suggest not updating for now.
Thanks for your quick answer !
@mchemin Fix is merged into master, we will notify once it`s published
@mchemin Fix is merged into master, we will notify once it`s published
Hi, I was wondering if you have an ETA for the release of version 1.0.8
Thank you!
@EtienneStPierre Its on our shortlist, we will post an update here when it
s released
Hello, are there any updates on when this fix will be released?
I would like to update to the latest version of react-native-keychain (v 7.0.0), but it adds a dependency on androidx.lifecycle:lifecycle-viewmodel:2.3.1, which breaks the Okta experience on my app for the reasons already described in this thread. It would be great if this could be fixed so I can upgrade.
I apologize for the delay. This has been released as https://github.com/okta/okta-oidc-android/releases/tag/1.0.19 Please note the change in maven coordinates.
Repro step
"androidx.lifecycle:lifecycle-runtime-ktx:2.3.0"
WebAuthClient#singnIn
Expected result The web client open with the correct login page
Actual result Okta SDK fails silently and the login page does not opened.
Suggested explanation We have observed that the call
OktaResultFragment fragment = new OktaResultFragment();
inOktaResultFragment
is done inside theRequestDispatcher mDispatcher
from theWebAuthClientImpl
class. The code from theRequestDispatcher
shows us that the instantiation of the fragment is done using a background thread executor.The
"androidx.lifecycle:lifecycle-runtime-ktx:2.3.0"
now forces fragment to be created on the main thread see the release noteEdit put the correct dependencies