@JosephCa Yes, disabling the permissions from Settings and restarting the app updates the UI to show that the user doesn't have screentime permissions anymore. When not restarting the app, the UI isn't immediately updated. But if you're using a button, which shows an alert if the user doesn't have access according to ‘AuthorizationCenter.shared.authorizationStatus != .approved‘ and otherwise would do some action, it would show the alert.

@vipulgupta012 Unfortunately not, I only could fix this issue by removing the AppIntentExtension itself and just use the structs in the normal App Target. So the easy solution for you would be First: Remove the TWAppIntentExtension and associated files except TWTAppIntent Second: Add TWTAppIntent to the main app target. That solved the issue for me. This also removes the need to have an extra extension for the AppIntent, which I think is quite neet as well.

Update: Yes, I needed the permissions for all of my app target. After receiving them, the error went away and it took 4 days to get the permissions. I didn't receive an email but as said before, you need to look under Signing & Capabilities for the certificate. If you still get an error, even though the certificate is available, you need to activate it under you certificates in the developer account.

A list of common App-URLs can be found here: https://github.com/bhagyas/app-urls

Thank you, that was the issue for me. I was wondering, why it didn't show the localizations I recently added to my Xcode project, but installing the language solved it.

@alasam No, unfortunately not. Still yet to find it

Hey thanks for your answer. I already included overriding intervalDidEnd, but decided not to mention it in the code snippet to keep it shorter. Here is my intervalDidEnd, do you have any further suggestions? It's still not working: ´´´swift override func intervalDidEnd(for activity: DeviceActivityName) { super.intervalDidEnd(for: activity) logger.log("INTERVAL ENDED") store.clearAllSettings() store.shield.applications = nil } ´´´

Hey @Quappi did you find the answer to your problem or is the issue something other than mentioned in my answer here?

Yes @Quappi you're right. Have you made sure that you didn't accidentally start a schedule in your case? You can fetch all the active schedules here with the following Documentation. You need to use the activities property and you can also additionally fetch the schedules times.

@Quappi Here are the steps you should consider: 1: Fetch all active schedules with this Documentation 2: Find the schedule that causes this issue 3: Track down how it's created (intentional or not) + fix 4: Additionally: You can see the default ShieldConfiguration in your provided screenshot. Is that the usual case or do you provide a custom one? If so, there may also be an issue regarding your ShieldConfiguration

Hey @Quappi I recently experienced something similar again. Simply going into settings and deactivating/ reactivating Screen Time access for all apps solved this issue for me. Everything works for me (for other apps providing the same functionality as well)

same thing! thanks for the help!