“iPhone 16 pro”

Thanks for the post. Unfortunately, there is no direct, programmatic way within the iOS SDK to automatically wake or launch your app specifically when the iPhone connects to CarPlay or a standard car Bluetooth system. Its important to mention your app is completely sandboxed from knowing anything about the CarPlay lifecycle. As a user, you can create a shortcut on your device. Open the Shortcuts app and go to the Automation tab. Tap + and select CarPlay or Bluetooth and select. The menu could be a little different. Set it to Connects and choose Run Immediately so it doesn't ask for permission every time like shortcuts do. For the action, they can select Open App and choose the app you want to run on the iOS device. Hope that give you an idea. I hope people do not provide you with ideas using Core Motion or Core Location to wake your app in the background when the user starts moving in a vehicle. It is advisable to avoid those options due to the potential issues they may cause. Albert
  Worldwide Dev

All apps should build with the latest SDK, so you have access to the latest APIs, regardless of the distribution mechanism used. Regarding the UIDesignRequiresCompatibility questions, it's useful to see how this was described in the WWDC25 Platforms State of the Union: As you evaluate your app's UI and the time you need to adopt the new design, we're providing an option to continue to use your app's current design with Xcode 26. We intend this option to be removed in the next major release. Hopefully you're on your way with the adoption of the new design already, or have upcoming plans to tackle it. You'll have to look at your own specific situations and determine how long you can continue using it for specific hot fix situations against the above statements and the timing of your own planned adoption of the new design. What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration chal

Hi, @Dominik_2 I'm a little late here but I'm having the same issue. Did you ever figure this out? I can't even get a 2019 Mac Pro to properly activate LOM and a 2023 Mac mini which gives me the same Address Already In Use error. Here's all my testing and info. Apple are you there??? Infrastructure: • Mac mini 2023 (M2, 10Gb Ethernet, MacMini.local, macOS 15.x Sequoia 15.7.4) — MicroMDM v1.13.1 • Mac Pro 2019 (MacPro7,1, Intel T2, MacPro.local, macOS 15.x Sequoia 15.7.5, T2 firmware 23P3120) • Both supervised via Automated Device Enrollment (DEP) through Apple Business Manager • Both enrolled: IsSupervised = 1, APNs working on both • Both are Controllers and Clients LOM Current State: Mac mini (Apple Silicon M2): • LOM profile installed ✓ • lom0 interface active ✓ • Port 55555 listening on * ✓ • LOMDeviceServerColsolidated path (Apple Silicon) ✓ • com.apple.AppleLOM.XPC active=1 ✓ • com.apple.AppleLOM.Watchdog active=1 ✓ • Mac Pro CAN reach mini's lom0 port 55555 — TCP connection es

after speaking on the phone, a support guy manually kicked off the email that gave me a link to https://developer.apple.com/contact/file-upload/upload/select to upload my ID, which I think was the missing step in the process. dunno if it'll work after that or not, but

0 libquic.dylib 0x36d84 quic_fc_service_pending_send_data + 360 1 libquic.dylib 0x3bcf0 __quic_conn_outbound_stopping_block_invoke_2 + 28 2 Network 0x23e428 nw_protocol_instance_access_flow_state + 136 3 libquic.dylib 0x3bcb8 __quic_conn_outbound_stopping_block_invoke + 744 4 libquic.dylib 0x3b754 quic_conn_outbound_stopping + 168 5 Network 0x3559b4 nw_protocol_implementation_finalize_output_frames(nw_protocol*, nw_frame_array_s*) + 576 6 Network 0x67308 nw_flow_service_writes(NWConcrete_nw_endpoint_handler*, NWConcrete_nw_endpoint_flow*, nw_flow_protocol*) + 5264 7 Network 0x58944 nw_endpoint_handler_add_write_request + 4860 8 Network 0x57880 nw_endpoint_handler_add_write_request + 568 9 Network 0x575a4 nw_connection_add_write_request_on_queue(NWConcrete_nw_connection*, NSObject*, bool) + 228 10 Network 0x5c314 nw_connection_async_if_needed + 76 11 Network 0x573c4 nw_connection_add_write_request(NWConcrete_nw_connection*, NSObject*) + 312 12 Network 0x56868 nw_connection_send + 516 13 CFNetwork 0x66b30 NWIOC