IssueTracker

Apps in Wear OS 5, that need to schedule exact alarms must:

Have this permission in AndroidManifest.xml

<uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM"/>

And then it also must ask for permission, from the user. How to do that is documented here:

https://developer.android.com/about/versions/14/changes/schedule-exact-alarms#migration

My specific app, Blose on Google Play, is requesting the permission dialog to be shown by doing this:

Intent intent = new Intent(android.provider.Settings.ACTION_REQUEST_SCHEDULE_EXACT_ALARM);
intent.setData(Uri.fromParts("package", "com.silentavalanche.blose", null));
startActivity(intent);

This works as expected in the emulator, and in Wear OS 5 on Galaxy watches, e.g Galaxy Watch 7 and Galaxy Watch Ultra. The permission dialog is shown, and users can give Blose permission to schedule exact alarms.

The permission dialog in Wear OS 5 on Pixel Watch 3 does however always come up blank, so users can't grant permissions to any apps. It has been like this since the initial release of Wear OS 5 on Pixel Watch 3, and it's still broken in the new release that just went out, i.e still broken in this release:

https://support.google.com/googlepixelwatch/thread/307540908?hl=en&sjid=9129724494237863258-NA

I don't think the app is doing anything wrong, since it's doing what the guide describes, and I also know of other apps that try to request the same persmission, and also fails on Pixel Watches with Wear OS 5. It's not like it's working for some. It's failing for everyone, and this leads to user frustration, and bad reviews, even though the problem seems to be in Wear OS 5 on Pixel Watches.