3 ms·

It works here. Running in a work profile, no contactless payments. Play Integrity API: Not blocked Hardened memory allocator: Enabled Memory tagging: Enabled

It works here. Running in a work profile, no contactless payments. Play Integrity API: Not blocked Hardened memory allocator: Enabled Memory tagging: Enabled Extended virtual address space: Enabled Secure app spawning: Enabled Native code debugging: Allowed WebView JIT: Disabled Dynamic code loading via memory: Allowed Dynamic code loading via storage: Allowed

dathinab 1mo ago
> no contactless payments. I think this is the problem here. A lot of NFC related tech is deeply rooted in having "trusted (aka large company)", "attested (aka you can't easily lie)", secure module functionality. What should have happened is to just not enable the contactless payment functionality for given app, even if the user enabled it in general. And not crash. Also as others have pointed out, this might be an accidental mishap not an intended outcome. But it's not like PayPal is known to care about small user-base edge cases (quite the opposite). Which I guess is the actual root problem.
- grapheneos 29d ago
  The issue turned out to be PayPal adding incorrect anti-tampering code incompatible with our secure app spawning feature. It's common for anti-tampering code to break real security features. It's a major reason for us having the per-app compatibility mode toggle and the finer-grained toggles for the individual exploit protections known to be incompatible with certain apps,
microtonal 1mo ago
Doesn't work here. No contactless payments, full Exploit protection compatibility mode.
- shaky-carrousel 1mo ago
  This is the PayPal version I have installed that works: Version 8.107.0 com.paypal.android.p2pmobile
  - microtonal 1mo ago
    Looks like I have 10.10.0. They'll most likely remove support for older versions server-side at some point.
    - super256 1mo ago
      I do have Version 10.10.0 since today and it also started crashing on open. Guess I'll have to downgrade to an older version for the time being.
    - shaky-carrousel 1mo ago
      That's weird because I keep all my apps to the latest version and still that's the version Google serves to me as the latest. Must be a regional thing.
      - microtonal 29d ago
        I think updates often use staggered roll-outs. https://support.google.com/googleplay/android-developer/answer/6346149?hl=en https://support.google.com/googleplay/android-developer/answ...
Groxx 1mo ago
This is my setup as well, though with JIT enabled (which is the default). Crashing at launch on: version 10.10.0 com.paypal.android.p2pmobile versionCode 1160090162 Seems pretty likely a flawed root detection being rolled out (given the stack trace), my phone is not rooted.
- grapheneos 29d ago
  The issue turned out to be PayPal adding incorrect anti-tampering code incompatible with our secure app spawning feature.

dathinab 1mo ago

> no contactless payments. I think this is the problem here. A lot of NFC related tech is deeply rooted in having "trusted (aka large company)", "attested (aka you can't easily lie)", secure module functionality. What should have happened is to just not enable the contactless payment functionality for given app, even if the user enabled it in general. And not crash. Also as others have pointed out, this might be an accidental mishap not an intended outcome. But it's not like PayPal is known to care about small user-base edge cases (quite the opposite). Which I guess is the actual root problem.

grapheneos 29d ago
The issue turned out to be PayPal adding incorrect anti-tampering code incompatible with our secure app spawning feature. It's common for anti-tampering code to break real security features. It's a major reason for us having the per-app compatibility mode toggle and the finer-grained toggles for the individual exploit protections known to be incompatible with certain apps,

microtonal 1mo ago

Doesn't work here. No contactless payments, full Exploit protection compatibility mode.

shaky-carrousel 1mo ago
This is the PayPal version I have installed that works: Version 8.107.0 com.paypal.android.p2pmobile
- microtonal 1mo ago
  Looks like I have 10.10.0. They'll most likely remove support for older versions server-side at some point.
  - super256 1mo ago
    I do have Version 10.10.0 since today and it also started crashing on open. Guess I'll have to downgrade to an older version for the time being.
  - shaky-carrousel 1mo ago
    That's weird because I keep all my apps to the latest version and still that's the version Google serves to me as the latest. Must be a regional thing.
    - microtonal 29d ago
      I think updates often use staggered roll-outs. https://support.google.com/googleplay/android-developer/answer/6346149?hl=en https://support.google.com/googleplay/android-developer/answ...

Groxx 1mo ago

This is my setup as well, though with JIT enabled (which is the default). Crashing at launch on: version 10.10.0 com.paypal.android.p2pmobile versionCode 1160090162 Seems pretty likely a flawed root detection being rolled out (given the stack trace), my phone is not rooted.

grapheneos 29d ago
The issue turned out to be PayPal adding incorrect anti-tampering code incompatible with our secure app spawning feature.