Various Google Apps stop working with microG (YouTube, Maps, Gmail, Google Opinion Rewards, etc.)

[cuynuissue]

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:

1. Install/Update Opinion Rewards with versionCode 2019049870, Google App with versionCode 301437738, Gmail with versionCode 64884528, Maps with versionCode 1067838727, YouTube with versionCode 1550046656
2. Open affected apps
3. See error. It says that Play Services isn't installed or exit itself if installed without old previous app data, Account login function also does not work at all

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

Details

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

Details

Additional context
This might also affects to more Google apps in future

[cuynuissue]

I tried with 0.3.5.240913, but its still the same, nothing changed.

[mcgi5sr2]

0.3.2.240913-21 same issue.

I think their is another issue open that covers this, so potential duplicate

[cuynuissue]

0.3.2.240913-21 same issue.

I think their is another issue open that covers this, so potential duplicate

it affects any microG version, as far as i tested from 0.2.26 till 0.3.5

[cuynuissue]

I think their is another issue open that covers this, so potential duplicate

i don't think so, there just issue about Maps doesn't work

[LZeugirdor]

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.

[Tentos]

I have installed com.google.android.googlequicksearchbox and tried to capture possible errors with LogFox.

I have stumbled upon the following messages:

1733945761.615 10281 24955 24983 W GoogleApiManager: The service for ctpu is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
1733945761.615 10281 24955 25984 W GooglePlayServicesUtil: com.google.android.googlequicksearchbox requires Google Play services, but their signature is invalid.
1733945761.615 10281 24955 25984 E GooglePlayServicesUtil: GooglePlayServices not available due to error 9

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

[stanwood77]

Confirmed. Same issue on /e/OS Version 2.5T stable (Android 13) - Fairphone 4 not rooted.
Google calendar + Google mail stopped working last night further both app updates.

microg version 0.3.2.240913-102 (d28f5bc)

[personofnorank]

Confirmed issue on e/OS 2.5, Fairphone 5 unrooted, MicroG 0.3.2.240913-102

[mar-v-in]

Google seemingly has updated their signature checking code. On Android 9 and above, the latest code uses PackageInfo.signingInfo (via GET_SINGNING_CERTIFICATES flags) instead of PackageInfo.signatures (via GET_SIGNATURES flag). This will likely roll out to non-Google apps in the future as well.

This means that all signature spoofing patches need to be updated to address the change of API usage by - in addition to the PackageInfo.signatures also spoofing the PackageInfo.signingInfo. There's unfortunately nothing we can do in microG itself.

[zykure]

@tjanez
Thanks, can confirm this solves the issue for now! I also had to downgrade Calendar on FP4 / microG 0.3.2.240913-102 (d28fb5c):

• Google Calendar:
  • Version: 2024.46.2-700284849
  • Version code: 2017604273
  • https://www.apkmirror.com/apk/google-inc/calendar/calendar-2024-46-2-700284849-release-release/

[mar-v-in]

Someone already submitted the patch from @jonathanklee to LineageOS: https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/411374

[pnaf]

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:

A fix is available and will be deployed through an OTA update early next week.

[cuynuissue]

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 -hw variant? i think fake-signature also must be updated with new spoofing method

[ale5000-git]

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?
Since the way signature spoofing is handled is different the problem may be different or may not happen.

[dimka40185]

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? Since the way signature spoofing is handled is different the problem may be different or may not happen.

Huawei has no problems, everything works as it worked. No problems

[grenadin]

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? Since the way signature spoofing is handled is different the problem may be different or may not happen.

Huawei below P60 was found the problem with this. Above P60 was perfect with 0.3.3 and 0.3.5

[ale5000-git]

Here's a summary of the situation:

• FakeGApps (fix merged) - v6.5 or higher contains the fixes
• LineageOS 19.1/20/21/22 (fix merged) - All builds from 2024/12/17 onwards contain the fix
• LineageOS for microG (fix auto-included from upstream) - All builds from 2024/12/17 onwards contain the fix
• /e/OS (fix merged) - v2.6.3 or higher contains the fix
• crDroid (fix merged) - v15.0-20241225 or higher contains the fix
• CalyxOS 6.2.2 and 5.14.1 (fix merged) - New versions in the works
• IodéOS v5.8 or higher (fix included)
• DivestOS (no info yet)

[pnaf]

/e/OS 2.6.3 or higher contains the fix: https://community.e.foundation/t/feedback-for-v2-6-3/64267

[brainchild0]

@ale5000-git: My general understanding is that the vendor rolled out updates of the user applications, which broke under unofficial environments, but not under the official environment, the combination of AOSP and GApps.

Presumably, users of the latter received updates for various lower and upper layers in tandem, even applying without full system upgrades, that preserved interoperation.

In contrast, resolutions being promoted in the current discussion depend on full system upgrades.

The general sense of my question is how users of environments based in LineageOS or microg might have an experience comparable, in terms of continuity, to the experience generally provided to the vendor.

[ale5000-git]

@ale5000-git: My general understanding is that the vendor rolled out updates of the user applications, which broke under unofficial environments, but not under the official environment, the combination of AOSP and GApps.

Yes and no, it is true that it break only in unofficial environments but just by coincidence.
Signature spoofing is used to make microG spoof the signature of official GApps.
GApps is already itself so obviously doesn't need it and it is unaffected :-)

The API used to check signature may return the result in 2 different ways; previously only the first way was used by apps and so previous signature spoofing patches patch only the first way.

Now the Google libraries used by various apps (so inside the various apps) got updated to use the second way of the API (the API is inside the system, so it can't be changed without a full system update).