Cannot log in to any instance - oauth error?
Meganium97 opened this issue · comments
Whenever I try to log into my main account on mastodon.social, I am able to approve the request, but I am then greeted with this:
Attempting to log into my alt account on a misskey instance, froggie.town, I'm able to do the same but am now greeted with this:
I'm a bit perplexed on what all of this means. I'm not too sure where to go from here.
Cannot reproduce on mastodon.social with master branch.
Any information regarding what version of the app you're running alongside the operating system?
I'm running android 13 on my Samsung galaxy s21fe using the latest release from f-droid.
I have same issue.
can't log in to misskey.io.
![image](https://private-user-images.githubusercontent.com/13450321/278971133-17d0d7bd-107e-4c8c-945b-a59cca116b51.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY2ODI3NDEsIm5iZiI6MTcwNjY4MjQ0MSwicGF0aCI6Ii8xMzQ1MDMyMS8yNzg5NzExMzMtMTdkMGQ3YmQtMTA3ZS00YzhjLTk0NWItYTU5Y2NhMTE2YjUxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAxMzElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMTMxVDA2MjcyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc2NzNkZjQ3Yjg4NmI3ZDc0NDBmOGZjNjBlNjc3ZDEwMzk0ZDFhMWM1ZjA3NDgwOWU4OGUwMzVmZmFkZGJlMzMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.VyHh18eeb8-7l3K7rAgT-FzYMjRX8298yRBRDqGGLnk)
developer tools error:
Failed to launch 'web+kaitekisocial://go-router-is-poop/oauth/misskey/misskey.io?token=this_is_dummy_string' because the scheme does not have a registered handler.
OS
- Edition: Windows 11 Pro
- Version: 22H2
- OS build: 22621.2506
- Experience: Windows Feature Experience Pack 1000.22677.1000.0
Browser
- Vivaldi 6.4.3160.34 (Stable channel) (64-bit)
Failed to launch 'web+kaitekisocial://go-router-is-poop/oauth/misskey/misskey.io?token=this_is_dummy_string' because the scheme does not have a registered handler.
Seems like Kaiteki wasn't registered as a protocol handler. I'll look into providing another redirect URI.