-
Notifications
You must be signed in to change notification settings - Fork 26
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
Having an issue logging in to my minecraft account on the FTB app #584
Comments
I'm having this exact same issue rn, only I've never had mojang only microsoft, so we can rule out the migrating as the cause |
Same here. The browser window seems successful, but I get the same error in the app. Looking at the log, requests to https://api.minecraftservices.com/minecraft/profile return a 404 for me. |
If it returns a 404, you don't have a That goes for everyone in this issue. |
so you're saying we have to stick to a mojang account to use FTB ? |
No. I'm saying your Microsoft account has to own Minecraft: Java editon, be it from a migrated mojang account or you having bought the game with your Microsoft account |
Thanks Michael! I feel like an idiot, but that was it. I have 2 Microsoft accounts and I was using the wrong sign in. Thanks again! |
I'v had the same issue, i forgot the set a Profile ID after i purchased Minecraft: Java Edition. When i set the ID, it worked. |
Im having an issue logging into my minecraft account on the FTB app. Tried logging in via mojang, and it said migrated (which makes sense since i did migrate my account). Tried with Microsoft, (since i migrated my account), and it said failed, even though i made sure it was the right account information. It says something went wrong and its unable to fetch profile from minecraft account (no id found). But i logged into the minecraft with the same account information that i tried on the app. Im not sure how to fix it or how it works... Ive run minecraft multiple times through the official launcher and its still not working
.
The text was updated successfully, but these errors were encountered: