You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SDK version: 3.0.8
Android Version: 7.1.1 (didn't test on other versions)
On Android, Firefox's Tab Queue feature causes the web browser login flow to not work due to SDK's AuthActivity treating the login flow as cancelled before user runs the login flow.
Repro Steps:
Set Firefox as default Browser for Android.
In Firefox go to Settings -> General -> Turn on "Tab queue" (which requires grating access Firefox to draw over apps, Settings link should show in Firefox when turning this on for the first time).
Invoke SDK's AuthActivity from client app with no Dropbox app installed (to invoke browser flow) which causes AuthActivity to request Android to launch the login flow URL in a web browser which launches the Firefox browser to open the login flow URL.
Due to Firefox's "Tab queue" feature, Firefox opens the login flow URL internally but does NOT show it to the user. Instead it returns right away causing AuthActivity in client app to show again while also showing a Toast like UI from Firefox to open the queued URL.
User then opens the login flow with the Firefox Tab queue Toast UI which then does show the login flow URL in Firefox now.
When user completes login flow in Firefox the web login flow navigates back to client application.
Client app's AuthActivity when navigated back does nothing because the Dropbox SDK has no token associated with the completed login flow.
The reason for having no token in the Dropbox SDK in step 7 is because in Step 4 when Firefox navigates back to the client app, the Dropbox SDK handles this as a cancelled login attempt and wipes its internal state (same would happen if user task switches back to client app while on Login flow in browser). This logic can be seen in
// We somehow returned to this activity without being forwarded
(onResume() will be called for the second time when Firefox navigates back to client app while mAuthStateNonce is non null -> authFinished(null))
For now I'm advising users who report this to simply turn off Firefox's "Tab Queue" feature or install Dropbox however it would be ideal if this just worked for users.
The text was updated successfully, but these errors were encountered:
@atulgpt No, unfortunately I don't have an update on this from the team, but I'll share your note about it also happening in split screen and multiple screen devices with them. Thanks!
SDK version: 3.0.8
Android Version: 7.1.1 (didn't test on other versions)
On Android, Firefox's Tab Queue feature causes the web browser login flow to not work due to SDK's
AuthActivity
treating the login flow as cancelled before user runs the login flow.Repro Steps:
AuthActivity
from client app with no Dropbox app installed (to invoke browser flow) which causesAuthActivity
to request Android to launch the login flow URL in a web browser which launches the Firefox browser to open the login flow URL.AuthActivity
in client app to show again while also showing a Toast like UI from Firefox to open the queued URL.AuthActivity
when navigated back does nothing because the Dropbox SDK has no token associated with the completed login flow.The reason for having no token in the Dropbox SDK in step 7 is because in Step 4 when Firefox navigates back to the client app, the Dropbox SDK handles this as a cancelled login attempt and wipes its internal state (same would happen if user task switches back to client app while on Login flow in browser). This logic can be seen in
dropbox-sdk-java/src/main/java/com/dropbox/core/android/AuthActivity.java
Line 412 in c710ef8
onResume()
will be called for the second time when Firefox navigates back to client app whilemAuthStateNonce
is non null ->authFinished(null)
)For now I'm advising users who report this to simply turn off Firefox's "Tab Queue" feature or install Dropbox however it would be ideal if this just worked for users.
The text was updated successfully, but these errors were encountered: