-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clientAppUnavailable from getDetails #640
Comments
It looks like DelegationService in AndroidManifest.xml is templated relatively as However, what is insane is that after I made that single change I haven't been able to break it again. I've reverted every change I made, and it still works. Even the known broken build I pushed to the Play Store Internal Track yesterday is working, and it also works on a different device too. So either something was very sad on my dev device (despite many uninstalls, reboots etc.), there was a transient issue with the Play Store, or perhaps there's some kind of trust relationship between the app and play store which needed to expire(?) or take effect. Very strange - but seems to be working for me now. |
As another update, I just installed my app onto another phone with a separate play account but which has access to the Internal Track and I receive the same error. I'm not sure if users have to be added to the Licence Testing configs as well, so I've tried that and am waiting to see what happens in the morning after some time passes. |
What helped me was using: |
@Stevie-Ray @tristan-morris, we also are hitting this error and have detailed it in #805, and using Stevie's logcat command we see that we also have a scoping issue, but we have no idea what needs fixing? Could you take a look?
|
I just ran into a problem similar to this. The problem was that my TWA was using 'http', but the app was registered to scope 'https'. I was running my TWA at It looks like bubblewrap always assumes scope of https:
I fixed things by manually editing |
I faced this problem and found out that in my case the problem was linked to Deep Link intent-filter. I removed android:autoVerify and android:sspPattern options, replacing the last one with android:pathPrefix. Also, check that android:host is specified correctly. |
Describe the bug
After calling
await window.getDigitalGoodsService('https://play.google.com/billing')
,getDetails(['pro'])
returns aclientAppUnavailable
error. I Googled"clientAppUnavailable"
and got a single result. I've poked around a bit but don't appear to have made much progress, however, I'll continue to poke around.I've had a PWA published in the Google Play Store for close to 18 months now. With the hopeful stabilisation of the Digital Goods and Payment APIs I'm trying to add in-app play billing support. Since my TWA codebase has remained fairly stable and has aged, I re-built from scratch using bubblewrap 1.15 late last week, followed the various prompts, reinstalled android and other deps as prompted (honestly, a very sweet experience - this is amazing!!! Well done guys!) I ticked yes to billing, alpha, notifications (the other clientAppUnavailable error) etc. Built the apk. Verified asset links remained correct. Joined v1 and v2 origin programs etc.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Returns a list of products.
Screenshots
N/A
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
Any pro-tips would be great! Thanks and awesome product!
The text was updated successfully, but these errors were encountered: