-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Various Google Apps stop working with microG (YouTube, Maps, Gmail, Google Opinion Rewards, etc.) #2680
Comments
I tried with 0.3.5.240913, but its still the same, nothing changed. |
0.3.2.240913-21 same issue. I think their is another issue open that covers this, so potential duplicate |
Family link login also seems to be broken after updating to 2.42.0.T.702836465 Downgrading to Family Link 2.41.0.S.703253343 worked |
it affects any microG version, as far as i tested from 0.2.26 till 0.3.5 |
i don't think so, there just issue about Maps doesn't work |
Can confirm this is happening for me on Calyx OS on the Pixel 4A. Gmail JUST got updated and is no longer working, my google voice has been out all day today and yesterday. |
I have installed I have stumbled upon the following messages:
Unfortunately, I cannot interpret the meaning of "signature is invalid" - maybe the spoofed microg signature is no longer considered up to date? I can upload the entire log file if necessary (I will however have to make sure that no sensitive information is included). Device: OnePlus 6, /e/OS T 2.5; microg version 0.3.2.240913-102 |
Confirmed. Same issue on /e/OS Version 2.5T stable (Android 13) - Fairphone 4 not rooted. microg version 0.3.2.240913-102 (d28f5bc) |
I can confirm, latest Google Drive app can't find my Google account. I will give the logs here. EDIT: I only found this sentence from the logs: Device information: |
Confirmed issue on e/OS 2.5, Fairphone 5 unrooted, MicroG 0.3.2.240913-102 |
Here are the versions I needed to downgrade to in order for the Google Apps to start working again with microG 0.3.2.240913-21 (9f758d8) that comes with CalyxOS 6.2.0:
The steps for downgrading:
|
Google seemingly has updated their signature checking code. On Android 9 and above, the latest code uses This means that all signature spoofing patches need to be updated to address the change of API usage by - in addition to the |
This comment has been minimized.
This comment has been minimized.
@tjanez
|
Since plain LineageOS does support signature spoofing, did anyone submit this issue to them? |
Someone already submitted the patch from @jonathanklee to LineageOS: https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/411374 |
Downstream projects such as /e/OS have begun applying the patch: https://gitlab.e.foundation/e/os/android_frameworks_base/-/commit/2b9c74a4409f41924905c4b28aa900904e442992 I also saw this announcement from a few of /e/OS's social media accounts:
|
is it can be included on next microG Service Core update? I wonder if lineage-microG also apply this patch |
"microG Service Core" is an app, the patch is for the ROM so it is completely unrelated. The patch for LineageOS isn't yet merged, once merged it will likely be picked up by every other ROM. |
what for |
On the -hw version is Huawei that handle the signature spoofing, so only Huawei can change it. But are you sure that Huawei is also affected by this issue? |
As @ale5000-git says
The Lineageos for microG project will monitor the progress of the patch in the LineageOS gerrit. We will only act if LineageOS decide not to merge the patch |
Speech Recognition & Synthesis (com.google.android.tts) is also affected.
|
Huawei has no problems, everything works as it worked. No problems |
Some major Google Apps stopped relying on the deprecated `packageInfo.signature` field and started using `packageInfo.signingInfo` instead. This commit introduces spoofing for the `signingInfo` field to maintain compatibility. Unfortunately, spoofing the `signingInfo` field is is a little more involved than spoofing the `signature` field, because the former relies on a `SigningDetails` class which is not part of the public SDK API [1]. We rely on reflection to instantiate the `SigningDetails` object, and to find the associated `SigningInfo` constructor. See also: - microg/GmsCore#2680 - https://gitlab.e.foundation/e/os/android_frameworks_base/-/commit/2b9c74a4409f41924905c4b28aa900904e442992 [1] https://cs.android.com/android/platform/superproject/+/1c19b376095446666df2b2d9290dac3ef71da846:frameworks/base/core/java/android/content/pm/SigningDetails.java
The fix for CalyxOS is being tracked here in case you come looking for it: |
It's still not working for me, same error. Did it work for anyone |
you need to reboot after enable fakegapps, it working for me with latest youtube app and maps |
There's still a fix awaiting for Android 9 to 12, if that's your case. whew-inc/FakeGApps#25 |
Hi, sorry to bother you and thanks a lot for your work! In this case I have: SPIC give errors of pictures and apps too (in picture I try to open Calendar updated version, with old ther's no problems like others GApps). Thanks a lot for your work and your attention, I'm really so glad to talk and read about you! |
@porcoddiocanebastardo You are using Android 12. Did you try the fix I just mentioned: whew-inc/FakeGApps#25 ? |
I have try now! Thanks a lot!!! |
This comment has been minimized.
This comment has been minimized.
The code was merged in the upstream lineage-21.0 branch at 20:52 yesterday. Looking at the `MicroG LineageOS builds' Matrix room I think that lemonadep should be the first build to have the fix. Other devices will pick up the fix in due course as they are built
|
Adding to this:
|
This comment has been minimized.
This comment has been minimized.
Once the patch rolls out live will it be safe to update apps or should we stick to older versions still? |
of course, yes |
Huawei below P60 was found the problem with this. Above P60 was perfect with 0.3.3 and 0.3.5 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Here's a summary of the situation:
|
/e/OS 2.6.3 or higher contains the fix: https://community.e.foundation/t/feedback-for-v2-6-3/64267 |
Affected app
Name: Google Opinion Rewards, Google App, Gmail, Maps, YouTube
Package id
com.google.android.apps.paidtasks
com.google.android.gm
com.google.android.googlequicksearchbox
com.google.android.apps.maps
com.google.android.youtube
Describe the bug
Google Apps including Opinion Rewards, Google App, Gmail, Maps, YouTube stopped working since last app update
To Reproduce
Steps to reproduce the behavior:
2019049870
, Google App with versionCode301437738
, Gmail with versionCode64884528
, Maps with versionCode1067838727
, YouTube with versionCode1550046656
Expected behavior
Apps should works with account, does not show any dialogues show that it doesn't have Play Services installed.
If i downgrade these affected apps to older version, it working again.
Screenshots
System
Android Version: 14
Custom ROM: LineageOS 21 :
21-20241101-microG-akari
microG
microG Core version: 0.3.4.240913
microG Self-Check results: All ticked
Additional context
This might also affects to more Google apps in future
The text was updated successfully, but these errors were encountered: