Skip to content
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

User cancelled flow #1038

Open
jinpengnice opened this issue Jan 26, 2024 · 3 comments
Open

User cancelled flow #1038

jinpengnice opened this issue Jan 26, 2024 · 3 comments
Labels

Comments

@jinpengnice
Copy link

Authorize custom tags by opening them in the upper right corner of the browser for authorization. Upon returning to the app, a prompt appears: AuthorizationException: {"type": 0, "code": 1, "errorDescription": "User cancelled flow"}. However, I did not cancel the authorization and simply replaced the custom tag with a browser. Opening the browser does not result in the correct result

@anhquan291
Copy link

anhquan291 commented Feb 11, 2024

Hi I'm facing the issue that there is no callback after cancelling the browser.
Have you found the way yet @jinpengnice ?
Really appreciated if anyone can help with this. Thanks a lot

@sanlee888
Copy link

Steps to reproduce it:

  1. Calling AuthorizationService.performAuthorizationRequest(authRequestBuilder.build(), completeIntent, cancelIntent)
  2. In the new version of CustomTab, there is a new "minimize" icon right next to the "X" icon. That is for the picture-in-picture mode. Click on that "minimize" icon, so now the customTab is in PIP mode.
  3. Our app receives "cancelIntent" with AuthorizationExeception.
  4. Restore CustomTab from PIP mode to normal mode.
  5. User continue the login flow, but app won't receive "completeIntent".

@oksuzozkan
Copy link

I am experiencing the same issue with the authorization flow in AppAuth-Android on devices running Android 12, 13, and 14. When I attempt the login process, the authorization code is not successfully returned to my app, and it fails to redirect back to the application.

This issue does not occur on devices running Android versions 8.1.0 through 11. In these versions, the login flow works seamlessly, and the app correctly receives the authorization code and returns to the app as expected.

I have also tried testing with Chrome version 130.0.6723.59-672305933 (com.android.chrome_130.0.6723.59-672305933), but this did not resolve the issue on Android 12, 13, or 14.

Any insights or recommendations on this issue would be greatly appreciated.
Screenshot_20241030_093725
#1034

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants