Fixed
Status Update
No update yet.
Comments
go...@stijnvandewater.nl
Fixed in ag/I491cdb1553fcaa0107d9cda78cb821c7cc62e92a and ag/I29df9a5c2dbd599b30a1fa95581d29052e8c143c.
sa...@google.com
ad...@google.com
Thank you for reporting this issue.
Can you share a bug report from the Wear device?
go...@stijnvandewater.nl
Hi,
I have created 2 new AVD's (Android Virtual Devices). One device running SDK 33 and the other one running WearOS SDK 30 (WearOS 3)
I have started logging on both and reproduced the issue using the demo project which can be found on:
https://github.com/android/wear-os-samples/tree/main/RuntimePermissionsWear
Attached the logs.
I have created 2 new AVD's (Android Virtual Devices). One device running SDK 33 and the other one running WearOS SDK 30 (WearOS 3)
I have started logging on both and reproduced the issue using the demo project which can be found on:
Attached the logs.
ad...@google.com
We have passed this to the development team and will update this issue with more information as it becomes available.
go...@stijnvandewater.nl
I cannot access the slide.
But I was well aware of this change. My question is that I cannot get the provided demo (https://github.com/android/wear-os-samples/tree/main/RuntimePermissionsWear ) to work after compiling with SDK33 even though everything is set correctly according to the documentation. You can try it yourself
Am I missing something? I can only imaging that this change breaks pretty much every WearOS app when targeting SDK33
But I was well aware of this change. My question is that I cannot get the provided demo (
Am I missing something? I can only imaging that this change breaks pretty much every WearOS app when targeting SDK33
ad...@google.com
The issue has been fixed and it will be available in a future build.
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Other issue
When did this happen?
Jun 11, 2022 11:31 GMT+02:00
What steps would let us observe this issue?
1. Clone the following git to your machine:
2. Open the project in Android Studio
3. Change the compileSDK to 33 (Tiramisu)
4. Sideload the wear app to a WearOS device
5. Sideload the phone app to a device
6. Keep the app for the phone in the background and try tapping the "Phone information" button the wearOS device
What did you expect to happen?
Activity opens on the phone
What actually happened?
Logcat throws:2022-06-11 11:29:04.850 1863-6517/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=com.example.android.wearable.runtimepermissions/.IncomingRequestPhoneService }
2022-06-11 11:29:04.850 1863-6517/? W/PackageManager: Access blocked: ComponentInfo{com.example.android.wearable.runtimepermissions/com.example.android.wearable.runtimepermissions.IncomingRequestPhoneService}
2022-06-11 11:29:04.850 1863-6517/? W/ActivityManager: Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=com.example.android.wearable.runtimepermissions/.IncomingRequestPhoneService } U=0: not found
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
High
Additional comments
I am fully aware of the change in the behavior as stated in the Android 13 developer documentation. But I am unable to get this to work after changing the compileSDK to 33, even the official example provided by you stopped working even though all the intent filters seem to be configured correctly
Debugging information
Google Play services
com.google.android.gms
Version 221820044 (22.18.20 (190400-451484765))
System App (Updated)
Android System WebView
com.google.android.webview
Version 500509933 (102.0.5005.99)
System App (Updated)
Network operator: Ben NL
SIM operator: Ben NL
Filed by Android Beta Feedback. Version (Updated): 2.26-betterbug.external_20220504_RC03
To learn more about our feedback process, please visit