[quote='820572022, kgaidis, /thread/771947?answerId=820572022#820572022, /profile/kgaidis'] my vote is that we get rid of these sort of policies all together as sticking to a clear rule [/quote] I’m fine with that!

[quote='822829022, Engineer, /thread/773290?answerId=822829022#822829022'] If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here. [/quote] I have the same question / feedback, filed under: FB15544362

[quote='743998022, Frameworks Engineer, /thread/724041?answerId=743998022#743998022'] Unfortunately, displaying a DeviceActivityReport in a widget is not currently supported. Please file an enhancement request using Feedback Assistant. Thanks in advance! [/quote] Hello @Frameworks Engineer! Is there any update on this? It’s now exactly two years since this was brought up…

Coming back to this because I’ve just encountered the same error message in my Xcode logs: Connection invalidated to streaming unzip service. Have you been able to figure out what’s going on? A delete and re-install fixes it as a workaround, but I would like to address the underlying issue.

[quote='817090022, Jimscard, /thread/764848?answerId=817090022#817090022, /profile/Jimscard'] I want them to go through the AI prioritizer [/quote] Thanks for sharing your thoughts, however the Developer Documentation specifically says that Time Sensitive Notifications break through Notification Summary and Focus: Time Sensitive notifications are similar to active notifications, but can break through system controls such as Notification Summary and Focus. About setting the trigger to nil causing undefined behavior, that’s completely wrong as well, as you can read in the documentation: trigger: The condition that causes the system to deliver the notification. Specify nil to deliver the notification right away. Again, thanks a lot for sharing your thoughts here, I’m specifically interested in the workaround you mentioned using PushKit. Could you share more details on this?

I am now on the iOS 18.2 beta. On my iPhone 15 Pro the issue came back. It’s not as bad as on iOS 18.1 but it’s very inconsistent. Sometimes it takes 5 seconds for the push notification to show up. Before, push notifications would show up instantly. That’s also what the API is meant to do. Super strange that Apple can’t get insane recession under control.

[quote='766686021, Natlay_E1, /thread/766686, /profile/Natlay_E1'] Why is my screen time doing this??? [/quote] It’s probably because you have updated your phone to iOS 18. Please see this recent thread for more info (there is not solution, Apple has not yet provided info if / when this software bug will be addressed): https://forums.developer.apple.com/forums/thread/766640

[quote='766640021, Juls__, /thread/766640, /profile/Juls__'] I updated my iPhone 13 to iOS 18 a few days ago [/quote] Hello Juls! This is quite likely the reason why you’re seeing the issues. Apple has introduced a series of software glitches in the recent iOS updates, especially when it comes to screen time and the screen time API. Glitches like the one you have described are frequent and happen on both Apple’s Screen Time tool, as well as third party apps that rely on Apple’s Screen Time API (they are forced to use the same underlying buggy technology stack as Apple’s Screen Time, so it makes sense that problems and glitches are shared). I had documented this in FB13696022 a while ago, so Apple knew about it and could've prevented it – but apparently Screen Time is not important enough so that one of Apple’s engineers actually looks at it :/ One thing I could recommend you to try is to turn off "Share across devices" at the bottom of Screen Time settings. Hope that helps!

@coderkid do you have Apple Intelligence enabled on your phone? Others & myself have been experiencing issues that Apple Intelligence is slowing down the whole system (we saw 10 seconds and higher delays) on iOS 18.1. I would recommend trying to turn off Apple Intelligence and see if it still reproduces. Also, definitely file a radar! I hope this gets fixed before iOS 18.1 gets released, otherwise we would have to recommend our users to turn Apple Intelligence off until Apple fixes the performance issues. More info here: https://forums.developer.apple.com/forums/thread/764848

I reported the same issue here: https://developer.apple.com/forums/thread/764848 For me, updating to the latest iOS 18.1 beta 6 resolved the issue (I am on a iPhone 15 Pro).

Hello everyone, I wanted to get back to this, it’s October now and we’ve seen some new iOS betas. Did anyone of you find a workaround for this issue? I’m on the latest iOS 18.1 beta and I can still reproduce this problem every day. As suggested by Apple in June, I have: Filed a radar Created a sample project to reproduce Filed a DTS ticket Even after 5 months: no responses. I am very frustrated by their non-existing help with this issue.

which iOS version are you on? For me, the picker regularly crashes / disappears completely (iOS 18.1).

Hello, due to privacy restrictions, bundle IDs are only available in the ShieldConfigurationDataSource. Otherwise they are nil / not provided. Hope that helps!

@amalshyjo the issue you're seeing could be related to a bug that has been talked about in these posts: https://forums.developer.apple.com/forums/thread/732845 and https://forums.developer.apple.com/forums/thread/758325 This bug was introduced by Apple in iOS 17.5 in spring 2024, however until now they have not responded to our feedback reports. I think it would be useful if you could file a feedback report on this as well, highlighting your perspective on the problem. Hope that helps!

That’s great feedback. AppStore guideline says: User-Generated Content: Apps with user-generated content must include: • A method for filtering objectionable material. • A mechanism to report offensive content promptly. • The ability to block abusive users from the service. • Published contact information for user support. And also: We treat all developers the same. So, Twitter’s update should be rejected!