Thank you again for taking the time to get this feedback to the correct place, I really do appreciate it, and it gives me hope that it may be addressed in the next major OS version. I did leave quite a few comments across the forums with the same feedback number, that was just to tie all these together as duplicate requests :)

Thank you so much Albert! I've found around 5–10 similar issues across the developer forums so far, and I'm sure there are more, so I'm not the only one with this issue.

Hi Quinn (the legend)! My feedback was specifically regarding the device's volume buttons, but that should be sufficient. When I filed a Feedback Assistant report, there was no AlarmKit category, so I had to file as an "other" category and as a "suggestion". I fear this will never be triaged to reach the correct team. Are you able to pass this on to the correct team, and possibly ask for an AlarmKit category for it to reach them in future? Thank you for your response!

It is still very limited, and importantly, volume buttons will just completely silence the alarm with no way to reverse this. Please pass on this feedback to the engineers working on AlarmKit: FB22686646

Having the same issue here. When either of the volume buttons are pressed, the alarm rings silently forever. FB22686646

I am able to build my app with a new bundle ID, but not the already existing bundle ID. I am unable to confirm if also adding a capability fixed anything as I did this at the same time as changing the bundle ID unfortunately. However, I still have issues that I want to build my app with the current bundle ID.

I am able to build my app with a new bundle ID, but not the already existing bundle ID. I am unable to confirm if also adding a capability fixed anything as I did this at the same time as changing the bundle ID unfortunately. However, I still have issues that I want to build my app with the current bundle ID.

I am able to build my app with a new bundle ID, but not the already existing bundle ID. I am unable to confirm if also adding a capability fixed anything as I did this at the same time as changing the bundle ID unfortunately. However, I still have issues that I want to build my app with the current bundle ID.