microg
Unable to Log In (Quest 2)
Describe the bug Normally this would not be an issue for most devices, because they're standard ROMs and not a large VR operating system. The problem in this case is with logging in. When I attempt to log in to my account with GmsCore, it refuses and throws an error like: "There was a problem connecting with Google's servers."
To Reproduce Steps to reproduce the behaviour:
- On any application, or in the GmsCore settings, find an "Add Account" button.
- Navigate through the menu and try to log into your Google account as you normally would.
- See error.
Expected behaviour When attempting to log into your account, the process should be handled properly and you will be logged in.
System Android Version: 12.1 Custom ROM: Meta Horizon OS
Additional context This issue is to be expected, considering the strange use case. I am trying to log in to YouTube ReVanced. The issue is present on ReVanced's fork, and this version of the GmsCore.
If I'm not wrong YouTube ReVanced use a custom version of microG, so it shouldn't have anything to do with official microG. So I'm not sure what you are reporting.
I'll try to give the info to them then, I'm still trying to figure this out in the meantime. Thank you!
If you can reproduce the same issue with official microG it may make sense to have this ticket, but if not then it only belong to their repo. Also if you are able to do it then a logcat would be helpful.
Pretty sure I'm using the official one right now. Going to take a nap, just to let you know.
Don't know if I did this right, I don't use ADB stuff much, but here ya go. Log's a fuckin mess with vsync duplicates and shit, dunno. I ran logcat without any flags directly to the file. shit.log
Describe the bug Normally this would not be an issue for most devices, because they're standard ROMs and not a large VR operating system. The problem in this case is with logging in. When I attempt to log in to my account with GmsCore, it refuses and throws an error like: "There was a problem connecting with Google's servers."
To Reproduce Steps to reproduce the behaviour:
- On any application, or in the GmsCore settings, find an "Add Account" button.
- Navigate through the menu and try to log into your Google account as you normally would.
- See error.
Expected behaviour When attempting to log into your account, the process should be handled properly and you will be logged in.
System Android Version: 12.1 Custom ROM: Meta Horizon OS
Additional context This issue is to be expected, considering the strange use case. I am trying to log in to YouTube ReVanced. The issue is present on ReVanced's fork, and this version of the GmsCore.
I had same error, just clear the storage and cache for revancedGMScore fork. And you are good to go. Worked for me
~~How do you clear the cache for a sideloaded app? adb?~~
adb shell pm clear com.revanced.android.gms
Still not working though. Ideas appreciated, let's solve this.
FYI also using the ReVanced GMS Fork or the original, both fail, the same way, even with a cleared cache.
Clearing anything regarding storage and cache helps nothing. I know only the communication between GmsCore and the Google Servers is bricked, but I cannot figure out the root cause of the issue. To clarify again, this is specifically an issue with Quest users. I'd assume that there's no compatibility with these devices automatically, and such is most likely the case.
@ale5000-git offtopic, but since I saw it a couple of times. Sometimes, we redirect people who experience problems with GmsCore forked on our end (ReVanced) to upstream if we assume the issue occurs upstream with the mention to use upstream GmsCore to reproduce the issue beforehand. I figured I'd mention it to clarify.
@oSumAtrIX The problem is that the logcat will report filename and line that obviously do NOT match and this will make the report almost useless. When redirecting users it would be nice if you inform them (before report) to remove the custom microG, install the official microG and then take a logcat with it. If both official microG and ReVanced microG are installed at the same time it will create a mess in the log and probably also additional problems.
@Meolsei I took a quick look at your log and I see a lot of errors regarding droidguard. It would be better, if possible, to have the logcat with all revanced apps completely removed, to be able to see the problem more clearly.
@oSumAtrIX The problem is that the logcat will report filename and line that obviously do NOT match and this will make the report almost useless. When redirecting users it would be nice if you inform them (before report) to remove the custom microG, install the official microG and then take a logcat with it. If both official microG and ReVanced microG are installed at the same time it will create a mess in the log and probably also additional problems.
Hi, this is what we do. I'll make sure to be clearer in the future.
@Meolsei I took a quick look at your log and I see a lot of errors regarding droidguard. It would be better, if possible, to have the logcat with all revanced apps completely removed, to be able to see the problem more clearly.
I only had YouTube installed, and even then, it was never opened from what I am aware. I only opened the standard (nom-forked) GmsCore and logged in from there. Will I need to make another logcat later? May be a few hours because I feel ill.
Also, sidenote and completely off topic from the main issue, but I'm sorry if my responses are sparse. Same issue that I've mentioned already, I'm just ill and trying to rest.
If I'm not wrong YouTube ReVanced use a custom version of microG, so it shouldn't have anything to do with official microG. So I'm not sure what you are reporting.
I have tried all of the official version or the third custom version of microG, all of the version have the same problem: can't loggin the google account with 400 error code. Maybe Google changed their API?
Hello all, I think this is probably because Horizon OS (Probably) doesn't ship with Google, This solution https://github.com/microg/GmsCore/issues/2560#issuecomment-2377593227 worked for me.
Hello all, I think this is probably because Horizon OS (Probably) doesn't ship with Google, This solution #2560 (comment) worked for me.
I can also confirm that this comment worked for me as well with Quest 3s.
