Status Update
No update yet.
Comments
co...@protonmail.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
uc...@google.com
je...@google.com
sp...@google.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"
co...@protonmail.com
co...@protonmail.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
co...@protonmail.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
sp...@google.com
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
co...@protonmail.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.
sp...@google.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!
co...@protonmail.com
@
Thank you for the update @
sp...@google.com
Android 13 is out today and we still have no patch unlike what you said a month ago
co...@protonmail.com
sp...@google.com
This issues has been already given high priority (updated external priority on this bug to reflect internal status). The fix is on the way and going through the final rounds of testing, so the roll out is slated to next couple of weeks.
To reiterate what have been mentioned earlier on this bug: this issue affects only apps targeting Android 13, so the apps won't break unless you bump targetSDK version to 33. In case if you want to start working on app compatibility for Android 13 behaviour changes, you could use
sp...@google.com
sp...@google.com
- The report is 2 months old
- Google chose to release Android 13 with that bug
- There's no mention of this bug on the documentation so you can totally bump your targetSdk without noticing it
So thank you guys for working on this but it's still not a valid excuse for taking that long for such an important issue. Now that being said, let us know when a fix is available
sp...@google.com
co...@protonmail.com
That must be some really intense testing as we are 10 days later and still nothing on sight. I don't want to be a P2 issue if that's what a P1 is.
Description
You can see some of my investigation in this threadhttps://github.com/firebase/firebase-android-sdk/issues/3966
My hypothesis is either AGP 7.4.0-alpha09 has something broken that prevents builds to firebase app distribution OR app distribution needs something changed so that it can handle these builds.
I do not have a minimal repro project. Everytime I try to prune down my companys project, the uploads to firebase work again.
What I can say for certain is that if I switch from AGP 7.4.0-alpha09 to AGP 7.3.0-beta05, then everything works. If I move back to AGP 7.4.0-alpha09 then I can't upload into firebase app dist BUT I can upload to play store. I'm generating apks (not bundles) in all cases as I have not switched to aabs yet.
To continue my research I'm going to try to go from alpha01 to alpha09 and see which one breaks.