While avoiding Google is a great idea and I want to do it as much as possible, I am finding it hard to avoid using Google Wallet for tap-in type payments and services. Presumably some apps may find it hard to take payments without it also (I’m moving from iOS tho so haven’t used apps in this way on Android).
At the moment Google Wallet does not seem to work for me. Is this a known problem, or does it work for some people? The error I get is:
Not yet supported com.google.android.gms.pay/homescreen.VIEW_HOME
If a known problem, are there plans to support the functionality needed, or is it just too complicated or risky given the link to financial transactions etc?
Thanks @marcdw — I did indeed check the forum but the posts seemed a bit old and potentially out of date, or just accepted that Google Pay was a non starter.
And thanks for the GitHub ticket, it seems like the question has moved towards being a bit more resolvable from a technical standpoint. It is kind of incredible that there is a duopoly in this space, somehow the regulators have missed something there!
Good point about the forum posts. Things move rapidly sometimes with Android. What was reported not working “yesterday” may now have a solution “today”.
Even though I may say search the forums I usually do so myself just in case something has changed regarding a subject.
What may or may not work regarding Google Pay seems unclear. In more than one place I’ve seen reference to success with a certain bank (mbank?) working somehow. Maybe some magic was involved (root, modules, safetynet workarounds, etc.).
The main microG dev, mar-v-in, did mention that the TapAndPay API is not implemented. That seems to be a major stumbling block I think.
when I’m in doubt, I search microg for the class. Even if it exists, it could be implemented superficially - so an App will not crash, but not have feature parity.
