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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃殌 Feature: Improve Missing Redirect URL Page for Mobile #3930
Comments
For me, not only the page is still open as it redirects back to do a new login on google, even after the log has been executed.
My AndroidManifest.xml has already the setup:
|
@FernandoUFS, it seems you're facing a different problem. Please join us on Discord if you need help troubleshooting. |
Any updates to this issue here yet? Just checking |
I also have the problem of missing url error like a flash. Besides this, Can anyone tell me why the value of the variable session is null? The code works, I can log in but the variable remains null.
EDIT: I solved this issue. I removed <model.Session> from FutureEither<model.Session> loginWithGoogle. |
Perhaps we can update the console page to show a different message if project is included in the query param. For reference, this is the Console code for the "Missing Redirect URL" page: https://github.com/appwrite/console/blob/30f0a3dd84cb914ca345effe6f472bed09776798/src/routes/auth/oauth2/success/%2Bpage.svelte#L10 |
I've been doing some testing and I'm slightly concerned about auto-closing the window/tab because it would trigger a user-canceled exception. |
馃敄 Feature description
For mobile apps, the default oauth2 page is used to redirect the user back to the mobile app via the
appwrite-callback-[PROJECT-ID]
URL scheme. The only problem is the Missing Redirect URL page is still shown and visible which can be confusing/annoying to users. It would be nice if the page closes automatically.馃帳 Pitch
Closing the page automatically would make the flow less confusing and clean up tabs/windows no longer needed. Either that or show a page that says "You may close this page now"
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: