I have a banking app which works on LineageOS (no gapps). It just checks if root is present and gives a warning then.

On Graphene the app works at the first start, but after that it gets stuck at the waiting screen (without any notification).

What could be the problem here? It only happens when I install Sandboxed Google Services.

    Blzzrd It only happens when I install Sandboxed Google Services.

    Why don't you install it on a user profile that doesn't have Google Services then?

      For some reason it doesn't work too... And I need gservices in my main one.

        Blzzrd for compatible Banking apps please see this community resource put together by a fellow moderator:

        https://privsec.dev/apps/banking-applications-compatibility-with-graphheneos/

        Also to try everything you need:

        • to install all 3 play services apps in order (just use the Play Store listing in the 'Apps' app which will take care of this)
        • then install your banking app
        • run it
        • if it crashes again then open the Banking app 'App Info' pane (can be done by long pressing the icon or via SETTINGS>APPS>SEE ALL) and enable the Exploit Protection Compatibility Mode
        • run it
        • if it crashes then go to SETTINGS>SECURITY and disable Secure Exec Spawning
        • run it

        If the above steps fail to work or even if they do file a report to improve the resource linked above here:
        https://github.com/akc3n/banking/issues/new?assignees=&labels=&template=app_report.yml

            a month later

            Just wanted to update this with a couple additional points.

            Banking apps project is now located at:
            https://privsec.dev/banking

            The issue form template has been updated today to include Pixel 7 series as well as our per-app exploit protection compatibility mode option.

            I've created a post on some common solutions that may resolve some banking apps compatibility issues:
            https://akc3n.page/banking-issues

            9 months later

            • [deleted]

            • Post #7
            • Edited

            MetropleX

            Users should first try Enabling Native code debugging, as enabling Exploit Protection Compatibility Mode literally disables hardened_malloc (for that app), which has more security implications than enabling Native code debugging. Having only Native code debugging enabled works in majority of the cases and I don't think disabling Secure app spawning will fix anything. Exploit protection compatibility mode should only be enabled for that app If it does not work even with Native code debugging enabled.