We are experiencing similar issues. This is what we can see in device logs: com.apple.network cloudd nw_parameters_set_source_application_by_bundle_id_internal Failed to convert from bundle ID (com.apple.FamilyControlsAgent) to UUID. This could lead to wrong data usage accounting. com.apple.network connection cloudd nw_endpoint_flow_validate_delegation [C112 Hostname#1d0a693b:443 in_progress parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, ipv6, dns, uses wifi)] Network Delegation Failure: Invalid Bundle ID "com.apple.FamilyControlsAgent" [I] com.apple.SwiftUI Invalid Configuration ActivityPickerExtension No symbol named '' found in system symbol set

Also: com.apple.cloudkit CK FamilyControlsAgent BUG IN CLIENT OF CLOUDKIT: requesting to use CPU QualityOfService UserInitiated while current thread is running at CPU QualityOfService Utility. Overriding with the following behavior: operation.configuration.discretionaryNetworkBehavior = .nonDiscretionary operation.configuration.automaticallyRetryNetworkFailures = NO operation.qualityOfService = .Utility As a rule of thumb, CKOperation should not run higher than CPU QoS Utility. For more information please refer to the header documentation for -[CKOperationConfiguration discretionaryNetworkBehavior].

We experience the same thing. Apps installed/reinstalled after iOS 18 upgrade. Running in simulator iOS 18 works fine. I've attached the crash report. App crahes at every run, both AppStore users and running from Xcode debug mode. Restarting the phone worked, but not ideal for real users... Is this a known issue? SomeApp-2024-09-30-204410.txt

We’re still seeing a dyld crash at app startup on iOS 18.1.1 (22B91). The crash happens before our app binary is even mapped (main_executable_path_missing in crash log). Device: iPhone 12 Pro (iPhone13,3) iOS: 18.1.1 (22B91) Distribution: App Store build Feedback filed: FB20068209 Restaring the iPhone sometimes resolves it, but it’s happening in production and has been reported by multiple users. To what version (if any) should we recommend users to upgrade until this is solved?