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
Android device authentication #2498
Comments
Hi @ryukooo, I have a few questions because I don't quite understand the issue.
|
Thankyou @brandonpage,
yes. Occurs only if enabled.
This will be the standard Android web view.
Occurs in about 1 minute We apologize for the inconvenience, but please check. |
Hi @ryukooo, is there any additional information you can provide about this? If you can reproduce this in a Mobile SDK app you have built can you provide debug logs produced by the SDK? Is there anything else special about this setup? Have you disabled biometric or the device screen lock? I have been trying on and off to reproduce this over the last several weeks on Pixel 6 Pro, Fold and 8 Pro but haven't seen it once. |
I posted it on the Trailblazer Community, but I'll also post it here.
https://trailhead.salesforce.com/ja/trailblazer-community/feed/0D54V00007StX3hSAF
Please fill out the following details:
5.Steps to reproduce:
I am using SalesforceMobileSDK-AndroidV11.0.1,
Enable connected application lock on Android 14,
I think that the device authentication starts after logging in on the Android device.
If you close the application from the application history and start it up, the device authentication may not start up sometimes.
Sometimes the lock screen does not appear and transitions to the application
I would like to improve this as it is a security issue.Do you have any knowledge?
The same thing happened with the Salesforce Android app, but if the unlock screen did not appear, the Salesforce logo screen was displayed and the process did not proceed.
Is there a way to get if the same is unlocke
8.Error Log:
Attached is the occurrence screen for the Salesforce app distributed on the Store.
The text was updated successfully, but these errors were encountered: