Filed under FB14872048.

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>; }

This appears to be fixed in Version 16.0 beta (16A5171c). Tested with a device running iOS 17.5.1 and using the instructions in my original post.

@hijackieyang My team's understanding is this is resolved in the iOS 17.4 Release Candidate. We're seeing our crash rate decline substantially since that was released.

Confirming this remains to be an issue with Xcode 15.1 and iOS 17.2 using the instructions in this thread.

Confirming this still fails on Xcode 15.1 beta 3 and iOS 17.0.3 with the same sample code in the original post above. I'll update the Feedback Assistant report.

It looks like this is resolved in Xcode 15.1, according to the Xcode 15.1 beta 3 release notes!

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.

@eskimo Are there plans to revert this change? I have not seen any reference to this on the Xcode beta update notes. Between the VPN issue and speed of the debugger, I am spending an order of magnitude more time dealing with the reliability of my tools versus being productive.

Still occurring on Xcode 15.0.1 and iOS 17.0.3. No reply on the Feedback Assistant report.

Posted to Apple's Feedback Assistant with ID FB13253099