Status Update
No update yet.
Comments
vi...@gmail.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
pe...@knego.net
r....@gmail.com
"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"
[Deleted User] <[Deleted User]>
ma...@google.com
mo...@gmail.com
+1, can confirm it doesn't work on Android 13:=
2022-07-15 11:26:15.023 589-5347 PackageManager pid-589 W Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023 589-5347 PackageManager pid-589 W Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023 589-5347 ActivityManager pid-589 W Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found
r....@gmail.com
Note that I've been able to make it work by:
- Adding
<action android:name="com.google.android.gms.wearable.BIND_LISTENER" />in the intent filter - Removing
<data android:scheme="wear" android:host="*" />
But I feel like this is not something we should do
jo...@gmail.com
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
ma...@gmail.com
If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.
But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.
da...@gmail.com
As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!
fa...@gmail.com
@
Thank you for the update @
ma...@gmail.com
Android 13 is out today and we still have no patch unlike what you said a month ago
Description
From the end-user's perspective :
1. Anyone who is interested in using Google App Engine can browse for apps by category, read reviews, etc.,.
2. Install it directly into their own Google App Engine account (either associated to a normal Google account or a Google Apps user account).
3. Use it for a trial period and later pay for app ($9/month minimum + additional usage charges), of which Google pays the developer a percentage.
From the developer's perspective :
1. Any developer can build an apps on Google App Engine and mark their app as available for sale, from within Google App Engine dashboard.
2. Option to restrict source code download (on by default) for such paid deployments.
3. Option to specify the GData APIs used within the app.
Nice to have features :
1. Developers have options to mark specific versions as "stable", "development" and enable customers to move to latest stable version at their own convenient time (after N-days/weeks, automatic/on-weekends).
It will also be better to be part of the Google Apps marketplace, for which I believe Google App Engine and Google Apps folks will have to co-ordinate.
Star this if you are a developer betting on Google App Engine.