Every time I try to open screen time settings the setting app freezes and afterwards it crashes. I tried restarting the phone a few times.I even tried reseting the iPhone settings and it's the same. I have an iPhone 13 with 128 GB of storage. The storage isn't full. What can I do? In IOS 18 BETA 2

Hi Apple The screen time issue is still going on in iOS 18 Beta 2. I have submitted my report in feedback but there is no response yet. There is no other way of accessing the screen time settings. It just crashes. If I try to go to the locked out app, the only option that actually works is the OK button. You can’t dismiss or extend for 15 minutes. Whoever going through this issue please report in feedback

Hello, I am working on an app that schedules a device activity monitor from the screen time API. I noticed that sometimes scheduling an activity monitor won’t work and instead I see this log: Canceling request to […].DeviceActivityMonitorExtension because it exceeded its allowed time. What does this mean? What exactly is exceeding its allowed time? Would love to get some feedback on this so I can prevent this from happening. Thanks a lot for any help and have a nice day!

Hi there, We recently released our app and got one production crash that can not be reproduced by our developers. It happens only on iOS 17.5.1 and the crash seems to be related to STWebpageController init at app start. The crash number is increasing fast but we have no idea about why it happens. Please help us to check the crash report below: Role: Foreground OS Version: iPhone OS 17.5.1 (21F90) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x1a29fcf20 __exceptionPreprocess + 164 (NSException.m:249) 1 APP_NAME 0x105e9e344 crashpad::(anonymous namespace)::HANDLE_UNCAUGHT_NSEXCEPTION(objc_object*, char const*) + 700 (exception_processor.mm:306) 2 APP_NAME 0x105e9d640 crashpad::(anonymous namespace)::ObjcExceptionPreprocessor(objc_object*) + 2544 (exception_processor.mm:513) 3 libobjc.A.dylib 0x19a8a6018 objc_exception_throw + 60 (objc-exception.mm:356) 4 Foundation 0x1a1f03868 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 188 (NSException.m:252) 5 ScreenTime 0x226860b2c __31-[STWebpageController loadView]_block_invoke + 448 (STWebpageController.m:140) 6 UIKitCore 0x1a55ae418 __146-[NSExtension(UIViewControllerAdditions) _instantiateViewControllerWithInputItems:asAccessory:traitCollection:listenerEndpoint:connectionHandler:]_block_invoke.29 + 268 (NSExtension_UIKitAdditions.m:96) 7 libdispatch.dylib 0x1aa8a013c _dispatch_call_block_and_release + 32 (init.c:1530) 8 libdispatch.dylib 0x1aa8a1dd4 _dispatch_client_callout + 20 (object.m:576) 9 libdispatch.dylib 0x1aa8b05a4 _dispatch_main_queue_drain + 988 (queue.c:7898) 10 libdispatch.dylib 0x1aa8b01b8 _dispatch_main_queue_callback_4CF + 44 (queue.c:8058) 11 CoreFoundation 0x1a29cf710 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 (CFRunLoop.c:1780) 12 CoreFoundation 0x1a29cc914 __CFRunLoopRun + 1996 (CFRunLoop.c:3149) 13 CoreFoundation 0x1a29cbcd8 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420) 14 GraphicsServices 0x1e787c1a8 GSEventRunModal + 164 (GSEvent.c:2196) 15 UIKitCore 0x1a500490c -[UIApplication _run] + 888 (UIApplication.m:3713) 16 UIKitCore 0x1a50b89d0 UIApplicationMain + 340 (UIApplication.m:5303) 17 APP_NAME 0x104dbc5c0 AppMain + 444 (app_exe_main.mm:128) 18 APP_NAME 0x104dbc630 main + 12 (app_exe_main.mm:135) 19 dyld 0x1c607de4c start + 2240 (dyldMain.cpp:1298) Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001ebab742c __pthread_kill + 8 (:-1) 1 libsystem_pthread.dylib 0x00000001ff856c0c pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x00000001aa95aba0 abort + 180 (abort.c:118) 3 libc++abi.dylib 0x00000001ff774ca4 abort_message + 132 (abort_message.cpp:78) 4 libc++abi.dylib 0x00000001ff764e5c demangling_terminate_handler() + 348 (cxa_default_handlers.cpp:77) 5 libobjc.A.dylib 0x000000019a8c1e2c _objc_terminate() + 144 (objc-exception.mm:496) 6 ourSdk 0x0000000108d8bc40 FIRCLSTerminateHandler() + 500 (FIRCLSException.mm:0) 7 libc++abi.dylib 0x00000001ff774068 std::__terminate(void (*)()) + 16 (cxa_handlers.cpp:59) 8 libc++abi.dylib 0x00000001ff77400c std::terminate() + 108 (cxa_handlers.cpp:88) 9 libdispatch.dylib 0x00000001aa8a1de8 _dispatch_client_callout + 40 (object.m:579) 10 libdispatch.dylib 0x00000001aa8b05a4 _dispatch_main_queue_drain + 988 (queue.c:7898) 11 libdispatch.dylib 0x00000001aa8b01b8 _dispatch_main_queue_callback_4CF + 44 (queue.c:8058) 12 CoreFoundation 0x00000001a29cf710 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 (CFRunLoop.c:1780) 13 CoreFoundation 0x00000001a29cc914 __CFRunLoopRun + 1996 (CFRunLoop.c:3149) 14 CoreFoundation 0x00000001a29cbcd8 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420) 15 GraphicsServices 0x00000001e787c1a8 GSEventRunModal + 164 (GSEvent.c:2196) 16 UIKitCore 0x00000001a500490c -[UIApplication _run] + 888 (UIApplication.m:3713) 17 UIKitCore 0x00000001a50b89d0 UIApplicationMain + 340 (UIApplication.m:5303) 18 APP_NAME 0x0000000104dbc5c0 AppMain + 444 (app_exe_main.mm:128) 19 APP_NAME 0x0000000104dbc630 main + 12 (app_exe_main.mm:135) 20 dyld 0x00000001c607de4c start + 2240 (dyldMain.cpp:1298)

The screen time issue is still going on in Beta 2. I have submitted my report. There is no way of accessing the screen time settings. It just crashes. If you try to go to the locked out app, the only option that actually works is the OK button. You can’t dismiss or extend for 15 minutes. who else is having this same issue?

Since the day i updated ios18 developer beta, screen time stops working and it wont let me access my apps under screen time lock despite of entering right password. Urgent solution required asap. please do something

I'm getting an error when i try to open Screen Time. It keeps crashing and wont let me do anything after that.

On the iOS 18 Beta, I am experiencing an issue where I am unable to sign back into an app using Face ID after the app time limit has been reached. This problem occurs consistently and is preventing myself from accessing the app using Face ID.

The following is request authorization for familyControls: AuthorizationCenter.shared.requestAuthorization { result in // The request can either result in success or failure switch result { case .success(): break case .failure(let error): print("Error for Family Controls: (error.localizedDescription)") } } But the output is"Error for Family Controls: Family Controls is only available for child and teen iCloud accounts." I have added the "Family Controls" capability, How do I use "Family Controls"

The listening callbacks were not triggered for intervalDidStart and intervalDidEnd after successfully starting center.startMonitoring when I attempted to set a schedule with DeviceActivitySchedule at 20-minute intervals Is there anyone who can assist me? Thank you. Below you will find my code. let intervalLengthInSeconds = 20 * 60 let intervalEnd = Date(timeIntervalSinceNow: TimeInterval(intervalLengthInSeconds)) let intervalStart = Date() let schedule = DeviceActivitySchedule(intervalStart: Calendar.current.dateComponents([.hour, .minute], from: intervalStart), intervalEnd: Calendar.current.dateComponents([.hour, .minute], from: intervalEnd), repeats: false, warningTime: DateComponents(minute: 1)) let newActivity = DeviceActivityName(rawValue: "20minuteUse") Log("😯 \(String(describing: schedule.nextInterval))") do { try center.startMonitoring(newActivity, during: schedule) } catch { print("failed to start session: \(error.localizedDescription)") } class MyMonitorExtension: DeviceActivityMonitor { let store = ManagedSettingsStore() // You can use the `store` property to shield apps when an interval starts, ends, or meets a threshold. override func intervalDidStart(for activity: DeviceActivityName) { super.intervalDidStart(for: activity) // Shield selected applications. Log("😓 start-------") } override func intervalDidEnd(for activity: DeviceActivityName) { super.intervalDidEnd(for: activity) Log("😓 end-------") } override func intervalWillStartWarning(for activity: DeviceActivityName) { super.intervalWillStartWarning(for: activity) Log("😓 StartWarning-------") } override func intervalWillEndWarning(for activity: DeviceActivityName) { super.intervalWillEndWarning(for: activity) Log("😓 EndWarning-------") } } schedule.nextInterval ------ print: 😯 Optional(2024-06-21 08:34:00 +0000 to 2024-06-21 08:54:00 +0000)

let schedule = DeviceActivitySchedule( intervalStart: DateComponents(calendar: Calendar.current ,hour: 20, minute: 0), intervalEnd: DateComponents(calendar: Calendar.current ,hour: 22, minute: 59), repeats: true, warningTime: nil ) store.shield.applications = selectionToDiscourage.applicationTokens.isEmpty ? nil : selectionToDiscourage.applicationTokens store.shield.applicationCategories = selectionToDiscourage.categoryTokens.isEmpty ? nil : ShieldSettings.ActivityCategoryPolicy.specific(selectionToDiscourage.categoryTokens) store.shield.webDomains = selectionToDiscourage.webDomainTokens store.application.blockedApplications = selectionToDiscourage.applications try center.startMonitoring(.daily, during: schedule)

try center.startMonitoring(.daily, during: schedule) let schedule = DeviceActivitySchedule( intervalStart: DateComponents(calendar: Calendar.current ,hour: 20, minute: 0), intervalEnd: DateComponents(calendar: Calendar.current ,hour: 22, minute: 59), repeats: true, warningTime: nil ) extension DeviceActivityName { static let daily = Self("daily") }

So I updated my phone to ios18 beta and ever since then my phone will always crash when I enter screen time but any other application nothing will happen, my phone has gotten so much slower and heats up faster. Lags so much! I dont know what else to do. I have 107gb and my max is 128gb so I don’t see that as the issue. Especially since I can’t enter into my screen time. I waited it out for almost two or one week. it hasn’t changed. restarted my phone and everything. please help asap!!!

Any apps that I have screen time on for and needs a password to gain access to it. Repeatedly says password is incorrect when it actually isn’t. When trying to go into screen time in settings, as soon as I click on screen time, it kicks me out of settings and put me back on home screen.

My app allows users to select apps and websites to block using the Screen Time API. Lately I have gotten a bunch of emails from users who say that selecting one app also results in other apps of that family being blocked, even if they aren't selected in the FamilyActivityPicker. The most common example is Facebook. A handful of users have said that they selected Facebook to be blocked, but Messenger will be blocked as well (even though Messenger isn't selected, and they don't want it to be blocked). Does anyone know why this might be happening? It seemed to begin happening awhile ago after allowing users to block websites in addition to apps - not sure if that could have something to do with it.

I have experienced a consistent bug with screen time in IOS 18 DB1. It just doesn’t work, but the limits still function. I cannot access screen time settings (it just crashes) nor can I disable screen time from within a blocked app itself. Have not found any workaround. I have logged a feedback report, FB13932765 (Unable to open screen time settings, it just crashes) I Hope this can be looked at and resolved by the next update. Thanks, Felix

We are using the Apple ScreenTime API for monitoring the usage of device. As mentioned in the documentation (https://developer.apple.com/documentation/familycontrols), we are getting the family controls authorisation from the user. We also have added the ‘DeviceActivityMonitor’ app extension (https://developer.apple.com/documentation/deviceactivity/deviceactivitymonitor) to receive the schedule and event callbacks. We have a requirement in which we have to notify the user for every 15 minutes usage of the device in the specified interval. He can optionally select individual categories or applications for the 15 minutes notification. For monitoring the usage for individual categories or applications, we obtain the token by presenting the FamilyActivityPicker as discussed in this documentation https://developer.apple.com/documentation/familycontrols/familyactivitypicker. For simplicity in testing during the development phase, we reduced the 15 minutes to 2 minutes. The events callbacks are expected to be delivered as soon as the threshold is reached but there are some inconsistencies with the event threshold callbacks. Sometimes the event callbacks are deferred and delivered together, sometimes the event callbacks are not delivered at all, sometimes a few event callbacks are missed etc.

i’ve recently updated to ios 18. I previously had a time limits set for instagram on my phone , so if i am past my time limit i could just ignore the time limit and continue using the app, but after upgrading to ios 18, i simply cannot use the app after the 1 hour limit set by me. Sometimes it would open, but without sound. I have tried all the things like turning off downtime ,turning off app and webtime activity , adding the app to always allowed list and so on. still no better. I use an 11 pro max.

Brief & History Since iOS 17.4 and up we experience a lot of flakyness when it comes to DeviceActivity event thresholds. After a lot of testing and investigations inside system logs and filing countless bug reports we found a reproducible way why the event thresholds are not getting properly called. Findings Apparently when the device reaches near to max memory something called jetsamkills processes left and right. This means that the UsageTrackingAgent that (we think) is responsible for tracking the usage time of the device gets killed and doesn't recover until significant memory is freeing up on the device. How to test it yourself Use a slightly older device with ~ 3 or 4 GB of RAM Open a game or two that is meomry intensive (like Fishing Clash, yes..) and observe In the console logs you see something that only happens then: Process UsageTrackingAgent [39307] killed by jetsam reason highwater This happens often but recovers itself when the UsageTrackingAgent exceeds their 6MB memory limit. Yet the log looks like this: Process UsageTrackingAgent [39307] killed by jetsam reason per-process limit Once you kick the game, the memory is free and sometimes the event thresholds are calling in again. Defeating the purpose However this defeats the purpose of tracking usage time and shielding perhaps the playing app from being played after a certain amount of time! Feedback Assistant Ticket Here is the ticket with sysdiagnose, step by step and more information: FB13884981 Please fix this ASAP, this is such a pain for production users and their kids EVERY DAY.

I have a problem I have an iphone 12 and iOs 18 and when I go into settings and click on screen time it crashes my settings