I don't see why it shouldn't work - you can start a LiveActivity from within the app, so why not trigger one of these Intents? My hope is that they just haven't wired into whatever the 'context' would be when running in-app. If not, hopefully this fact can be documented

Just a quick note that this trick still works in iOS 26's light-mode tinting, and in 'clear' mode. Thanks! 🙏

Can confirm that this works, BUT - if you're not seeing the error in the Issue Navigator, make sure you're not filtering out warnings.

I just found the same error, using both Xcode 16 beta 6, and the new Xcode 16 RC, released today. The code that causes the crash: private class func roundOff(decimal: Decimal) -> Decimal { var rounded = Decimal() var raw = decimal NSDecimalRound(&rounded, &raw, 2, .plain) return rounded } The only occurs with Archive builds, and is crashing on iOS 17.6.1.

Works this morning - thanks for the info!

Thanks - will do!

Yep - that's what the App Store Connect Engineer informed us of. The idea that it should be version independent was definitely an assumption that I made, probably because both Deep Links and Custom Product Pages both already exist independently, and it didn't occur to me that it required a specific version of the App Store. I'd recommend filing a Feedback to back port it (although I'm not super hopeful that that would happen)

Oh snap, I didn't realize this was an iOS 18-only feature. When I run it on a device running the beta, the deep link does work, so that's my answer. This is a bit of a bummer - given that Deep Links and Custom Product Pages both already exist, I was assuming this would work on existing versions. It would be great to see this feature back-ported! (FB13988662 🙂)

Short update - I submitted this to the SwiftLint team, in the off chance that it's something they can address: https://github.com/realm/SwiftLint/issues/5619

@ISSD2022 - I believe this can be done today. Sound Recognition is a valid Automation trigger in the Shortcuts app (for a 'Personal Automation'), which can run any Shortcut, including 3rd Party Shortcuts and those that manipulate HomeKit devices. The problem is doing the opposite -- using a HomeKit trigger (motion detected, temperature triggers, etc) cannot run any 3rd Party Shortcuts. Incidentally, if you do want to run a 3rd Party Shortcut in response to a HomeKit event, I have added this capability to Signals for HomeKit on the Mac 👍