IssueTracker

For WearOS 5 (Android 14), android.permission.SCHEDULE_EXACT_ALARM is not granted automatically. The permission must be included in AndroidManifest.xml and then users must be taken to the appropriate permission screen using the following code:

                        Intent intent = new Intent("android.settings.REQUEST_SCHEDULE_EXACT_ALARM");
                        startActivity(intent);

This code takes users to the correct screen on the WearOS 5 emulator, and shows apps that are allowed/not allowed to schedule exact alarms. Alternatively on the WearOS 5 emulator, the user can go to Settings > Apps & notifications > App Info > (app name) > Advanced and can grant permission there. Neither of these options are available however on the actual Pixel Watch 3. The first method just shows a screen headed 'Alarms & reminders' with no apps shown. The second option is missing altogether from the Advanced settings page.

Consequently **there is no way for the user to grant this permission** on a physical Pixel Watch 3. This bug means that any app which requires this permission is completely non-functional.

The correct behaviour is that the Pixel Watch 3 should correctly respond to the code above, so that the user sees a settings screen for Alarms & reminders and can grant permission to an app that has requested this permission.

This is a security issue because it relates to an Android permission that can't be granted on a physical device, and therefore causes certain apps to be non-functional.

PLEASE READ:

This form is only for reporting bugs found in the Android system while
developing Android applications. Use the Developer Tools subcomponent for issues with
the developer tools. https://issuetracker.google.com/issues/new?component=192633

Please describe the problem in detail. Be sure to include:
- Steps to reproduce the problem (including sample code if appropriate).
- What happened.
- What you think the correct behavior should be.
- Is this a security related issue? Yes/No

Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).

Please also run "adb bugreport" and archive the output.

To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted (https://developers.google.com/issue-tracker/concepts/restricted-content)” when creating a bug or adding a comment. Restricting or deleting your comment or attachment can also be done using the overflow menu after submitting.

Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (https://policies.google.com/privacy), and you agree that we may share it with engineering partners potentially impacted by your issue.

Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes