[Google Pixel Watch 2] simplepinoi177:
That's weird and interesting....

If you weren't aware, there's a lot going on right now with getting Google services like Wallet and Play Store properly working. Google keeps shutting down the established method for essentially bypassing root detection -- case in point, chiteroman's PIF newest versions work for a very small limited time little bit before getting shut down/blocked. He's working hard to bypass each time and is constantly updating to a new version, but because so many of us rooted users use the module, it quickly gets flagged by Google and gets shut down.

Also SafetyNet has become depreciated and isn't a good indicator any longer for passing to get these services working -- Google's all about Play Integrity API now. As such, there are 3 or 4 Play Integrity checkers that are used now to check -- and if you'll use them, even on your watch, you'll find you most likely wouldn't pass.

There is a particular, special way to get the PIF (and PIF fork) bypass to stick, but it's a very involved process. If you really are interested and up for a

challenge

, you can start by looking at these two posts HERE and HERE; and if you want a safe space to seek some guidance, you can visit my thread. In any case, that's why you wouldn't pass (both in those checks and "meets security requirements")...

But even so, that's a weird issue about the timeout message and what not....it may be about not passing "integrity", or it might just be an app glitch. I suggest you force close the app, and clear cache. If you get desperate, "remove upgrades" and/or clear data (this will, obviously, clear any data/settings/cards).

I only got the "doesn't meet security" error when I first unlocked the bootloader and tried to launch Wallet without installing the PIF/Displax MOD module -- I don't think it ever happened when I tried adding a card and/or using the Tap to Pay (on second thought, I think I found out the PIF module doesn't work any longer because that's what it said when I tried to Tap to Pay).

In any case, while you might be able to launch the Wallet app with MEETS_BASIC_INTEGRITY (which is what I think you can at least achieve with PIF or Displax's MOD), unless you can pass both MEETS_BASIC_INTEGRITY & MEETS_DEVICE_INTEGRITY (I was able to run this Play Integrity checker (SPIC) to see those on the PW2 [the others, without a no-DPI version was impossible to navigate to work]), you can't load up your cards or use Tap to Pay.

Also, with those 2 modules, you never needed to Zygisk block the two apps, Displax and PIF (which is a good part based on Displax's MOD) worked under the hood to bypass/"block" them anyways -- so doing so on the watch (or phone for that matter) wouldn't be enough anyways...

But, good news is that if you are able to figure out how to search/find them "fingerprint", pick a promising one (off of certain criteria), implement and test it on your phone, you can do the same on the watch and the Wallet app on the watch works! I can attest to it -- I specifically went to the store to test it out and make sure I can Tap to Pay with both my PW2 and phone. One thing that happened that I thought I would have to do but didn't was re-enter the cards on my PW2 like I did with my phone....but as I was able to add my cards before Google shut down Displax's MOD, apparently even if it fails to meet security requirements at one point, once you get it to pass MEETS_DEVICE_INTEGRITY, you wouldn't have to re-add/reactivate them....

I know I threw a lot at you here, sorry about that. But I hope it helps...! Good luck to you!