App thinks phone is rooted

Plethora9278

Thanks - it's indeed probably been a glitch... :-/

mademoisellemabry

With GOS release 2026071100 we get the following change:

replace secure (exec) spawning feature with a new implementation with improved app compatibility and a per-app toggle replacing the previous global

I just checked and disabled secure app spawning for AGOV and it seems to work - now there's no sdk rooted message. I will test and implement accounts in the next days.

Novaliss

mademoisellemabry that is great news. 😊

Carrousel7956

HappyPanda67 It's fine, don't worry about it.

ElliesSurviving

i will just add here since the latest release which has that new secure app spawning implementation, no apps have complained about root for me anyways, none did before either and its still none now, i usually see revolut as the baseline for my phone as that is pretty strict on root detection therefore having a ton of false positives but it still works fine here

Plethora9278

mademoisellemabry Thanks for the hint - I'm on 2026071101 and in fact I was able to selectively disable app spawning for the AGOV app. I just don't know how to "migrate" from my old Pixel 5 to my GOS Pixel 9a: does anybody know how to?

mademoisellemabry

You need to log in to their web portal https://agov.ch/me and add additional credentials i.e. your GOS phone there (don't know the exact name right know). When it's all done, you can delete the older credentials (although I will keep mine for some time, just in case).

mademoisellemabry

Plethora9278 It's called Loginfaktoren in German.
Meanwhile I was able to add an account on my GOS device though having problems with another (but that got nothing to do with GOS). Seems to work.

Plethora9278

mademoisellemabry Thanks - I'll have to do it when I'm back home, as my working AGOV app is on an old Pixel 5 lying around at home...

Plethora9278

So back I am. The verification of the AGOV app configuration on my GOS phone requires to confirm a push notification - which does not arrive/appear. What might be missing now? The only missing right for the AGOV app is the "nearby devices" one.

Plethora9278

Did you know about this?
https://www.agov.ch/index.php?c=agovapk&l=en
Looks like there will be a GOS-compatible APK!

Jenseitsjens

Been following this thread for a while and just reopened the AGOV app today and there was no error!

I've been able to successfully set up my device without doing anything special and just successfully logged into AGOV. Can anyone reproduce this?

My Device details: Pixel 10a, GrapheneOS 2026080501, AGOV 4.1.2 from Google Play Store (apparently a version from end of July)

Plethora9278

Jenseitsjens Hi - did you verify if you already disabled "Secure app spawning"? Because with the default setting (enabled), AGOV tells me that my device is not supported.

I'm running GOS 2026081301 on a Pixel 9a with AGOV 4.1.2 from the Play Store.

On my end, I'm still unable to complete the activation (as posted back on the 26th of July if you scroll up you see it). Does anybody know how to proceed to complete?

mademoisellemabry

Plethora9278
Do you have notifications allowed for Google Play Store? I believe to remember that it is necessary to have Google Play Store installed and notifications allowed for the app to work (although I downloaded it from Aurora and am not logged into Google Play Store app).

mademoisellemabry

Plethora9278
Very interesting. So federal sideloading it will be 😄 Could this be a way for future government apps as well?

h34p

Downloaded today from Play Store, enabled "Exploit protection compatibility mode" and it worked.

Plethora9278

h34p What's the difference between "Enable exploit protection compatibility mode" and "Secure app spawning"?

Novaliss

Plethora9278
If you enable the compatibility mode, all of the exploit protections gets turned off for that app, including Secure app spawning.

Most apps work with the protections enabled, and there's very few apps that need you to turn all protections off. So, if you got the time to disable them one at a time and try again, that is better since e.g. Hardened Memory Allocator is almost never a problem for an app to run.

Jenseitsjens

Plethora9278 I was under the impression that I didn't customize anything but after rechecking I indeed did turn on "Exploit protection compatibility mode" (which disables Secure app spawning as well).

If I turn off that mode I get the SDK-Rooted error again.

I'm not quite sure what exactly changed, but previously I was not able to complete the whole process either, but when I tried it a week ago everything worked.

« Previous Page