Post

Replies

Boosts

Views

Activity

Reply to INPlayMediaIntent `mediaSearch` mediaName unreliable when searching for playlists
After looking into this further, is it possible that vocabulary registered with INVocabulary will appear as <null> instead of the vocabulary when on development devices? For example, on our main development device, we have a playlist registered via INVocabulary named "Country Bangers". When using the phrase "Hey Siri, play the playlist Country Bangers in ", we receive the following mediaSearch: <INMediaSearch: 0x101c587e0> { reference = 0; mediaType = 5; sortOrder = 0; albumName = <null>; mediaName = <null>; genreNames = ( ); artistName = <null>; moodNames = ( ); releaseDate = <null>; mediaIdentifier = <null>; } However, if we use the same phrase on a different test device without that playlist name in its registered vocabulary, we receive a mediaSearch that is, in fact, populated with the playlist name: <INMediaSearch: 0x126054780> { reference = 0; mediaType = 5; sortOrder = 0; albumName = <null>; mediaName = country bangers; genreNames = ( ); artistName = <null>; moodNames = ( ); releaseDate = <null>; mediaIdentifier = <null>; }
Aug ’24
Reply to Xcode 15, how to uncheck "Connect via network" for physical device?
Per @eskimo's comment above, I've "piled on" by submitting a Feedback Assistant bug report (FB13350507). Reiterating that I do not see how this is not an extremely high priority issue and I think that it is unreasonable to expect developers to continue working with these issues for months on end. Most notable issues stemming from this for myself and my team are: Debugging has become extremely slow. Breakpoints take 30-45 seconds to populate with information (such as variables in the current scope). Executing a command via LLDB takes a similar amount of time while Xcode is waiting to execute the command on the device. "Debug View Hierarchy" takes a very long amount of time as well. It is not possible to debug an app while a VPN is running. Our test devices will periodically lose connection or time out. This makes debugging a long running app session difficult if not impossible. Possibly unrelated, but we've noticed a spike in issues relating to code signing failures which necessitate the entire app to be reinstalled (which is particularly frustrating because Replace Container functionality is broken - see FB13253099). None of these apply if the device is connected via USB.
Nov ’23