We are also noticing issues with this, very likely since iOS 26.0. It seems to be connected to device being on charger - happened on my device two times already. My guess is that the charger makes the system run some background tasks for Screen Time and they incorrectly call that eventDidReachThreshold method.

Here it is side by side. Not sure why one simulator shows different time.

Hi, this seems to happen to our app also. We get lots of support messages from our users saying that their device activity threshold is reached before they spend the "allowed time" in the apps. Did Apple respond to any of the feedbacks? Is there any change in iOS 26.1?

Thanks! Just submitted - FB16477099.

This exists since iOS 16, I don't have any hopes of it being fixed... From what I managed to uncover it is memory issue since the picker runs in special extension and apparently has just handful of memory. I am not sure why Apple yet hasn't "simply" increase the memory limit. The Photos picker works fine without issues.

I have the same issue. Seems to be related to any widgetAccentedRenderingMode. Thanks for the workarounds! In my case Color.clear did not work, so I had to do: Link(destination: launchUrl(for: game)) { Color.black.opacity(0.001) }

Same issue with iOS 17... No matter whether it is the expanded view or compact, the Text with timer is too wide and I cannot do anything about it.

I can try prepare the project, but this issue seems to be around 1 in 10 or 1 in 20, it does not reliably appear in the main app.

Tried the phone support today and it is sorted 🙏 My trader info has been verified. So if anyone is in the same boat, I would recommend using the support page to request phone support during the day.

I know and I selected so 🤷🏻‍♂️

The "Resubmit" just points to - https://appstoreconnect.apple.com/business I am an individual.

How does "In Review" mean waiting for the information? I already submitted the info in March and currently have o options to submit any additional info nor revise the submitted info.

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.