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

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

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

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 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

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)

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

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.

This might be stupid question, but can it also can be adapt to a pre-compiled ROMs from a device that abandoned and no longer have any future rom development? My machine doesn't even enough for compile a AOSP ROM from source.

If Android version is less than 9, no change is needed. If 9 or higher you need to recompile the ROM yourself with the new patch or use FakeGApps.

So i have a question, as far as I see basically we do a small change in ComputerEngine and everything works fine again assuming rom already had signature spoofing.

I have an issue, I'm trying to build crdroid a12.1, now I can find this ComputerEngine in CrDroid a13 version and onwards, but what if you need to update the SignatureSpoofing prior to a13? Where would you look at then?

I have an issue, I'm trying to build crdroid a12.1, now I can find this ComputerEngine in CrDroid a13 version and onwards, but what if you need to update the SignatureSpoofing prior to a13? Where would you look at then?

The required change for A12 / LOS 19.1 is here

For A11 / LOS 18.1 a patch is available, as described in this XDA Forum post. LineageOS for microG used this atch successfully in their recent 'one-off' build run for 18.1 devices, to ge round this issue.

For A10 / LOS 17.1, the changes to AndroidManifest.xml and strings.xml from this patch. (The other changes in that patch are not needed.) See this post in the LineageOS for microG issue tracker for background on this change. And thanks to @Flamefire who is still making up-to-date builds of LineageOS 17.1 for working this out

I found google stealthily installed an APP, Android System Key Verification, which can't be found by manual search in google play store. It was installed without notification of user. After remove this the APPs seems working well. Not sure if this is the root cause of the issue.

@summerlovewarum
If you find it again could you please check the internal name of the app?

@summerlovewarum If you find it again could you please check the internal name of the app?

He is probably referring to the Android System Key Verifier.

More info here

@summerlovewarum If you find it again could you please check the internal name of the app?

He is probably referring to the Android System Key Verifier.

More info here

Yes. It's Amdroid System Key Verifier.

my phone is redmj note 5 and now microg doesn't open. if o click on open it doesn't show anything .I can't link google account to YouTube . anything to try .its android 14