I was struggeling with the same until I found that I had to add `NSAppleMusicUsageDescription` to my app's Info.plist otherwise the Intent extension would not be loaded – yes, even though I was not using the apple music library. This seems to be an undocumented requirement for extensions handling `INPlayMediaIntent`.That said, now everything works fine as long as I'm running Siri in english. In any non-english language, it doesn't recognize that my app is being referred to. I'm afraid this is a (yet another of way too many in the past times) bug in iOS.
Post
Replies
Boosts
Views
Activity
The recommendation seems to be to launch the actual playback not from the extension, but rather from the app. For this, return `HandleInApp` from `resolveMediaItems:`.
Indeed. They did it in version 4, but since then it accumulated so much cruft that it would be time to redo again.
It seems Apple recently partnered with TuneIn for their internet radio, that's why TuneIn Radio stations are seemingly implicitly a destination for Apple Media intents. I'm also working on an internet streaming radio player, btw.
It‘s always a bit unfortunate, when Apple deprecates a technology in place of a less capable one. There have been quite a lot of interesting widgets that are no longer possible with the timeline-based approach in WidgetKit. Sad.
Please make sure to report this to the Sherlock team.
Good question, I’m in the same situation. Pity that noone dares to share some wisdom here. It looks like much of the traffic has moved to forums.swift.org.
FWIW, I wonder especially whether it’s possible to (ab)use SPM for pure Objective-C packages. What did you settle for?
It's been a long time, but in the meantime, this bug has been fixed. It's working as of at least watchOS7 (maybe earlier).
Still in iOS 14.3 – I find it mildly amusing, but also irritating that Apple leaves such messages in their builds. It demonstrates a general sloppiness and lack of polish.
Same problem with my AppleWatch SE cellular. Unbearable!
How did you manage to get the CoreBluetooth security confirmation appear for your command-line app? I'm trying to do the same and said alert only appears when I run the app from lldb.
FWIW, the culprit is the missing inherited permissions. When running the tool from iTerm (which is what I'm using as terminal emulator), it inherits the permissions from it. Granting Bluetooth permissions to iTerm fixes my problem.
Now: Is it possible that my command line program can detect this lack of (inherited) permission, thus preventing the crash and rather showing an instruction alert instead?
Note that softlinks do not impose any problems. I have my DerivedData softlinked to a ramdisk volume and everything is pretty snappy that way.
Derive a custom application class and override preferredContentSizeCategory.
I can confirm this. The iPhone mini simulators are pretty much unusable as of Xcode 13. Congrats, this marks a new low in the release of Apple developer tools.