UBS TWINT

[suchprototype]

Is there an existing issue for this?

• I have searched the existing issues

App name

UBS TWINT

Link to app

https://play.google.com/store/apps/details/UBS_TWINT?id=com.ubs.Paymit.android

App version

42.2.0.158

Country of the app

Switzerland

Build Number

2024091900

Device list

Pixel 8 Pro

Profile app tested in

Owner profile

Google Play installed?

Not Installed

Where did you install this app from?

Aurora Store

Google Play services Network permission revoked?

• Revoked
• Not revoked
• I did not have Google Play services installed

Native code debugging

• Allowed
• Blocked

Exploit protection compatibility mode

• Enabled
• Disabled

Memory tagging extension (MTE)

• Enabled
• Disabled
• N/A

Dynamic code loading via memory

• Restricted
• Allowed

Dynamic code loading via storage

• Restricted
• Allowed

Stock OS compatibility

• Works
• Does not work
• Not tested

NFC payments

• Works
• Works but requires another service
• Does not work
• N/A (Not supported by app)
• Not tested

Description of the app's functionality

@spring-onion: Now requires Google Play.

Everything works. TWINT doesn't use NFC to do payments. You just need to scan a QR code to pay and it works great :)

https://www.ubs.com/ch/en/private/digital-banking/apps/twint.html

https://www.twint.ch/en/bank/ubs/

Are there any extra notes you think users should know about?

No response

ADB logcat of the app if necessary

No response

[spring-onion]

Great, thanks for all the reports!

[nicdumz]

@suchprototype on Twint v42.3.0.13 on a Pixel 8 I currently get UI flickers leading to crashes. Do you still have a stable UBS Twint?

I didn't really manage to get it stabilized.

Error logs reveal things like E chromium: [ERROR:aw_browser_terminator.cc(165)] Renderer process (12906) crash detected (code -1).

Attaching a W+ set of logs

TWINT log _ W+ 2d6c5251710f.txt

[Mo0-n]

I came here to report the same @nicdumz . @suchprototype does it still works for you?

Twint v42.3.0.13, tried on separate profile without play service. Installed with google play on owner profile.
Pixel 8 Pro

I have also flickering; the app eventually crashes. It happened only after attempting to transfer money (which didn't work - it worked with my former phone with stock OS just after) first time, then any subscequent use of the app had flickering. UBS banking app with access app works seamlessly.

New GrapheneOS user, i tried only to activate exploit compatibility mode, doesn't solve the issue.

After this, I tried on owner profile, where I have play services and orbot Tor VPN. Stopped the VPN (otherwise the twint app says "no connection", force stopped play store and play service, initialized access and twint and I could transfer money, no flickering.

But the point is that I don't want to use my Twint app in the owner profile, so it does not solve the issue for my use case.

EDIT for completeness: on the owner profile I restarted with orbot VPN and it works. I force stopped google play service and play store and it works after this still.

[spring-onion]

@nicdumz @Mo0-n It's not super unusual for a banking app to expect and/or need google play services.

I would like to know if it's okay with being in a secondary profile. Install google play there and let me know please. It's very rare for an app to refuse to work in anything but the owner profile, but it can happen.

[nicdumz]

Yes, you're right, it works fine in a (non-owner) profile with GPS installed.

Hardening+Memory tagging is fine. Blocking native code debugging is possible.

The app does try DCL via storage but works fine (?) if GOS restricts it. I might not have discovered the feature depending on Dynamic code loading.

[spring-onion]

Alright thanks for the info. Users who prefer to not run google play in their main profile can segregate it then.

[Mo0-n]

Thank you. I also confirm UBS Twint works in separate profile (not owner) with google play services (tested: parking fees & send money).