It does not work for me. I have a pixel 6a and just updated to android 13, still does not work. When I create a new work profile, is there anything that is defined by the main user? Is there any chance that it works when I reset the main user or reinstall it?

I also have problems with google maps sometimes: then the app opens and crashes. Overall I am not very happy with how reliable of is. Newpipe also stopped working for me and does not load any video.

Any ideas on what to do for trouble shooting?

When google maps cannot be opened, it works again after rebootibg the dsvice. Newpipe is just unusable now also after reinstalling.

    RubixCube when YouTube changes anything on their back end NewPipe breaks as it did recently. They have pushed an update and it is not related to the Android 13 update.

    As far as your TAN2go issue I suggest not using a work profile and trying in a proper secondary user. I am presuming you are cloning the 'Apps' app into the work profile to facilitate the install of play and not cloning the play services themselves. Again I repeat you must just use the Play Store listing in 'Apps' to install all 3 and not do them individually.

      6 days later

      @RubixCube have you checked back on your TAN2go app since the latest release? You can try going to App Info now and toggling on "Exploit Protection Compatibility Mode" to see if that helps in this use case.

      Let me know how you get on or if you:d manage to resolve this in the interim.

        I've got the same issue on grapheneos Android 13 with the dkb tan2go app like @RubixCube .

        The normal DKB banking apps work fine without google play (no notifications though).

        The tan2go app freezes at the dkb logo in the main user profile without g services, in work profile with g services and in another user profile with g services.

        enabling "exploit protection compatibility mode" does not work. Neither DISABLE_HAHRDENED_MALLOC or ENABLE_COMPAT_VA_39_BIT.

        MetropleX do you have another idea how to solve the issue?

            mobos after mentioning that I get it to the QR scan, the only thing I can recommend if you can't get it to do the same is to go to SETTINGS>SYSTEM>DEVELOPER OPTIONS>BUG REPORT>INTERACTIVE and then attempt to open the app with both Exec Spawning Toggle on (SETTINGS>SECURITY>ENABLE SECURE APP SPAWNING>ON) and Exploit Protection Compatibility Mode Off (SETTINGS>APPS>SEE ALL>DKB TAN2GO) then when it crashes disable exec spawning/secure app spawning and try again, followed by enabling the Exploit Protection Compatibility Mode for the app and try again. This way all attempts will be logged.

            Once done either

                MetropleX changed the title to DKB TAN2GO App Crash Issue .
                a month later

                MetropleX It's somehow frustrating to see that I did not reply for over a month, I am sorry for this.

                I tried it multiple times as well as trying multiple different methods. Sometimes I gave up too early and tried it another day without success either. I also tried the logging method but I have to do it one more time and contact someone. This is somewhat difficult and frustrating and takes time. It's easier to have another phone lying around.

                Anyway, thank you very much for your help. I hope I'll succeed with the logging method.

                    2 months later

                    Hi mobos Sorry for not replying earlier. Did you open a case or send logs yet? So far I use an old iPhone to use with this app but that's not a good solution. Did you log anything so far? Otherwise I will do that now and send it. Let me know.

                      MetropleX
                      I tried and tried,could not find the initialise.Login option only. So I re-flashed the OS again, to find the same situation.
                      Hop option to initialise.

                        2 months later

                        Hi, if you enable "native code debugging" in general settings, the app loads normally and seems to be working fine! This seems to solve the issue.