-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[9.2.0] oauth.authenticate no longer resolves after login on Android #247
Comments
I've done some further investigation - looks like the issue was introduced in this commit forcedotcom/SalesforceMobileSDK-Android@4bb9cca |
We will take a look, thank you for reporting! |
Encountering this issue as well. Following this thread +1 |
Hi @bhariharan @wmathurin @mjmasn did you find any workaround for this, i am facing this one as well. I am currently using v9.2.0 |
@AnuragTiwari1 I managed to solve this temporarily by reverting the change made on the commit that @mjmasn mentioned. |
Any update on this @bhariharan? |
Hi all, we are still aware of this issue and it is prioritized on the roadmap. This issue requires a careful fix which is why it is taking so long. Thank you for your patience! |
Experiencing same issue in v10... workaround still helps. Thank you very much! |
Any update on this?? |
Any update on this??. We are facing the same issue at version 11.1.0 of react native sdk |
Any update on this? |
This is a critical issue.
In our MainActivity.java we're using:
(and the equivalent on iOS)
When a user clicks login on our welcome screen, we call oauth.getAuthCredentials then if that fails we call oauth.authenticate. Since upgrading from 8.3.0 to 9.2.0 this authenticate call no longer resolves at all on Android.
I've whipped up a quick reproduction repo here: https://github.com/mjmasn/AuthIssue
The repo above contains a fresh app created with forcereact with the typescript template with the following changes:
false
from shouldAuthenticate() in MainActivity.javaGradle 7.3 pre-release so I can build with Java 17I reverted this and installed Java 11 to rule out any issues hereThe text was updated successfully, but these errors were encountered: