Thanks for the additional details. I guess my imagined use case is really outside the intended ones. My app connects to Nintendo Switch game console, which requires the user to initiate the connection on the Switch. The console then presents a QR code with WiFi network info (including the password which is different each time). So my app scans the code and uses the NEHotspotConfigurationManager to initiate the connection. My idea was to present the new "picker" after the QR code is scanned.

Okay, thanks. Guess I will have to stay with my current solution. My use case is that I am temporarily connecting to accessory which has different WiFi password each time that gets generated once the user initiates the setup on the accessory. My hope was that this picker would give me "completion" so I would know for sure when accessory is connected...

I read that, but my understanding was that this API is supposed to replace the entire pairing process and connecting to WiFi network with password is (at least in my opinion) part of the initial process.

Also the same issue on multiple App Store Connect accounts, including app where I have already ran A/B test for alternate icons.

Yes, this is known issue for months but Apple is not doing anything about it 🤷🏻‍♂️ I also have my own thread https://developer.apple.com/forums/thread/737948

I think my solution is the same as you have. I have a function that returns View for the bottom part (the game names + days until release) and I call it three times in the ViewThatFits and pass max number of items to render. I think the range is from three to five and that seems to work in most cases 🤷🏻‍♂️ Wish there was better solution though. Something like ForEachThatFits :D

We just run into the same issue, trying to run the intent from Spotlight results in Shortcuts error notification and when running the intent from interactive widgets, only part of the logic gets executed 🤯 I would have guessed prior experiencing this, that triggering App Intent would launch the app if it were quit before. Here is the error message from screenshot so others might perhaps find it: "The operation couldn't be completed. (WFBackgroundShortcutRunnerErrorDomain error 1.)"

Just opened feedback if anyone wants to reference it: FB13210566

I have also filled a feedback if anyone wants to reference it in their report: FB13092595

We are also noticing the same issues on iOS 17 now.

How do you know about that limit? Is it documented anywhere?

Will do, we have Feedbacks opened for various activity report issues but not this one yet.

Ended up with the ViewThatFits solution that tries to fit as many rows as possible.

Upon further investigations it seems these issues aren't iOS 16.6 exclusive. By digging through the Xcode Organizer (with the filter set to last year) I found similar ones for iOS 16.4 from April and later for iOS 16.5. But nothing prior to iOS 16.4. Since our app has been out on the day iOS 16 was released this is suspicious. Either the Organizer doesn't show the crashes or they weren't happening. Check the stats below:

Hello, with 16.4 there is now search - although it would be nice to be able to control the navigation title or be able to hide it.