3 ms·

With or without Google Play Services running?

• leumon 2mo ago
  With. But disabling "Secure app spawning" seems to fix it for now.
  • gib444 2mo ago
    Ew that's a nasty workaround. But interesting to know!
    • grapheneos 2mo ago
      Secure app spawning is a per-app toggle now so it doesn't reduce OS security or the security of other apps without it disabled. It only reduces security of the app with it set to disabled. If multiple apps have it disabled, they share the same ASLR bases, memory tags for memory allocated before fork and other things. It's one of the toggles changed by the per-app exploit protection compatibility mode. If an app doesn't work, that's the first thing to try. It can then be narrowed down to a specific setting. The more aggressive exploit protections uncovering a lot of compatibility issues are only enabled for the base OS and specific user installed apps by default. Those can be set to enabled by default for all user installed apps and then people have to deal with the per-app toggles a lot more. This applies to memory tagging, disallowing dynamic code loading via memory/storage and disallowing native debugging (ptrace).
      • gib444 2mo ago
        Thanks Daniel. Nice to see you back again tirelessly educating the community about GrapheneOS, almost no comment not replied to!
• grapheneos 2mo ago
  It's because PayPal shipped an update with incorrect anti-tampering code incompatible with secure app spawning. It can be worked around with the per-app secure app spawning toggle until they fix it.