Search results for

“iPhone 16 pro”

80,727 results found

Post

Replies

Boosts

Views

Activity

Reply to Apple Carplay iOS 18 and Toyota
I was having the same issue with my Toyota Sienna - iPhone 16 Pro was not connecting with CarPlay. The problem I found was due to a cheap USB cable (Type-A to Type-C) - this caused the CarPlay connection to flop, making it unusable. I swapped it for a higher quality cable (same Type-A to Type-C) and now the phone connects with CarPlay and stays connected. Its clear to me now that the quality of USB cable matters more with Type-C than it did with the older Lightning connector. It also may help to ensure your Toyota audio and navigation firmware versions are current - see https://www.toyota.com/firmware-updates - You can check the version installed in your vehicle, under Menu (the faceplate button) > Setup > Software Update. The website also provides clear instructions how to download and perform the software update using a USB flash drive (a dealer can do this for you, but I was quoted over $200 at Toyota Service, I opted to learn and do it myself.) My current configuration: iPhone 16
Jan ’25
Reply to LLDB RPC server crash in Xcode 16.3
Same here: lldb started crashing with simulator on encountering breakpoints, as of right now it even seems to crash reliably after some time. It seems to work properly on physical device Sequoia 15.4, XCode 16.2, iPhone 16 pro simulator 18.2 If that matters: I use github copilot xcode extension and that one also has issues => chat assistant crashes a lot and forces me to relaunch xcode every couple requests report.txt
May ’25
Reply to XCode 16 RC and Sequoia 15 RC - Running a XCTest UI test runs the test but does not open the simulator and initiating a record just hangs and never runs
@DTS Engineer Not OP but I am also seeing this issue on Xcode 16.0 (16A242d). I am attempting to run a test to an iPhone 16 Pro/18.0 sim and as @hogman78 said, sim never launches and test runner just hangs. Sim opens fine running & building, but not for UI tests. Tried resetting device (device > erase...) and building to something different, same behavior. Restarted MBP, no change. Sequoia 15.0
Sep ’24
Reply to MKMapView appears red on iOS 18 simulator + Xcode 16
I've had the same problem for a while now. I am currently using Xcode version 16.2 (16C5032a). The problem is with the iOS 18.2 and iPhone 16 Pro Max simulator. Not with the iPhone 15 Pro Max Simulator and iOS 17.5. I can also zoom up to 24 meters and the colors remain the same. The problem starts at a zoom range of 1500 meters and not everywhere. Play around with the coordinates from the simulator. It works in Cupertino, San Francisco or other large cities, but not in rural areas. In Europe, the colors are red almost everywhere when zooming.
Jan ’25
Reply to Can't install any apps on my new iPhone 16 Pro with iOS 18 from XCode
I was running into the same error with my newly acquired iPhone 16 Pro. I downloaded Xcode 16.1 beta 2 and successfully set it up for development. This morning my phone was updated to what appears to be the final iOS 18 version (as opposed to the version installed on new phones) and tried Xcode 16 (NON beta) again. This time the setup for development worked immediately. That suggests to me that Xcode 16 came with a package specifically for the final version of iOS 18, and not for the version shipped on new phones. Hopefully this will all be resolved soon between shipping phones with the latest OS version and updates to Xcode. FWIW, I updated my phone manually in Settings>General>Software Update.
Sep ’24
Reply to iPhone 16 Pro - iOS 18 camera crashing
UPDATED: I forgot to mention that I am not running a beta, this is the gold release that has this issue (But I feel like its a beta) and I only singed into the dev side to see if a beta might have the fix for this. I agree, it should be raised as a bug. But I also think this should have never been a bug with a new phone pro model that always focuses on the camera. I’ve had his issue also, along with photos not displaying correctly when I look at them from the camera app, videos recording without now sound. And in a time I needed it to work and document damage from the storm for insurance reason. At the price of a iPhone 16 pro max this was a big failure.
Topic: Community SubTopic: Apple Developers Tags:
Oct ’24
Reply to .contactAccessPicker shows blank sheet on iOS 26.1
Thank you! I’ve tested the sample project on several devices running iOS 26.1 (iPhone 16 Pro) and iOS 18.6 (iPhone 11). On the iPhone 11, both AddContactButton and QuickAddContactButton work as expected - I’m able to add new contacts to the Contact List. However, on the device running iOS 26.1, tapping AddContactButton opens a blank sheet (see attached screenshot). In the Quick-Add section, after pressing the 'View' button, the debugger shows the following message: #ContactsButton response after touch -- encountered an error: Button is occluded
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Nov ’25
Reply to NSCocoaErrorDomain Code=513 after user delete's
I can't reproduce the issue you described by building the sample app with Xcode 26.0 beta 5 (17A5295f) and running it on my iPhone 16 Pro + iOS 18.6.1 – After deleting the app's iCloud data with Settings, and going back to the sample app, I see that the documents I created disappears, and can create a new document without any error. What system version did you test with? I am wondering if the issue only occurs on an old system version... Best, —— Ziqiao Chen  Worldwide Developer Relations.
Aug ’25
Reply to Cannot run Animation Hitches Instrument
I see the same problem whenever I profile on a physical iOS device from Xcode 16.1 or 16.2 Beta 2 with any instrument using a recording mode of “deferred” (which happens to be the default recording mode for the Hitches tool). If I change the recording mode to “Capture last n seconds” (or, when available, “Immediate”), the errors do not appear. FWIW, my configuration is similar: M1 Mac Studio, Sequoia 15.1. Profiling a new blank project on iPhone 16 Pro Max, iOS 18.1.
Nov ’24
Reply to Callkit call blocking problem
In my case, when I try to block calls on iOS 26, the blocking doesn't occur; the scenarios seem intermittent. If I create two CallDirectory extensions, the first blocks the numbers, but the second doesn't. Interestingly, the extension marks the number as suspicious. There's also a case where, on iOS 26 on an iPhone 16 Pro, the functionality doesn't work at all. I'd like to know if there have been any changes to the use of CallKit in iOS 26, because users of my app on iOS 18 and below report successful blocking.
Topic: App & System Services SubTopic: General Tags:
Nov ’25
Reply to Sharing data between Targets via App groups but Userdefault Container is null
Main app bundle identifier: in.xxx.app Intent extension identifier: in.xxx.app.MuteIntent App group: group.in.xxxx.shared I have save value A in Main App target and B in Intent extension target against the same key and re-run the app. Both target have its own value which I saved previously. It means UserDefaults in not shared between targets. Also tested same behaviour with Message extension where UserDefaults sharing working fine. xcode: 16.2 iOS simulator: iphone 16 pro 18.1 Is it limitation with Intent extension (Siri)?
Feb ’25
Reply to Regression: Heavy Delay of Push Notifications on iOS 18.1 beta (10s and more)
This delay still occurs in iOS 18.1 RC (22B82) on iPhone 16 Pro when Apple Intelligence is enabled. This is an unacceptable amount of delay for time sensitive notifications, for example - push notifications from the Duo MFA application do not appear until 10-12 seconds, and the time out to response is only 20-30 seconds. I filed my own feedback fro this under FB15418918, which reports More than 10 similar reports. The only solution I've found is to completely disable Apple Intelligence.
Oct ’24
Reply to The iOS 26 simulator crashed due to NWPathMonitor
I was able to reproduce this as follows: Using Xcode 26.0 beta on macOS 15.5, I created a new project from the iOS > App template. I replaced ContentView.swift with the code you posted. I set the app’s deployment target to iOS 16. I ran the app on the iPhone 16 Pro / iOS 26 simulator. I suspect that you’re hitting the issue discussed on this thread. As suggested on that thread, I was able to work around this by adding this code to my App struct: struct Test789304App: App { init() { _ = nw_tls_create_options() } … } Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Jun ’25
Reply to After building the project, the search form does not allow typing, but pasting works.
The warnings you see are caused by Apple's code, not yours. It relates to displaying a keyboard, so you can ignore those. Just tried this here and it works fine. iPhone 16 Pro Max 18.2 Simulator. What happens if you click in the text field in your app in the Simulator, and press Cmd+K to toggle the software keyboard? Does it let you type into the field? Can you remove/comment out the .overlay that contains the clear button with image xmark.circle.fill. Maybe the tap onto the field is being intercepted by the Spacer() and that image? I don't know, I'm just trying to see what might cause your issue.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Feb ’25
Reply to Apple Carplay iOS 18 and Toyota
I was having the same issue with my Toyota Sienna - iPhone 16 Pro was not connecting with CarPlay. The problem I found was due to a cheap USB cable (Type-A to Type-C) - this caused the CarPlay connection to flop, making it unusable. I swapped it for a higher quality cable (same Type-A to Type-C) and now the phone connects with CarPlay and stays connected. Its clear to me now that the quality of USB cable matters more with Type-C than it did with the older Lightning connector. It also may help to ensure your Toyota audio and navigation firmware versions are current - see https://www.toyota.com/firmware-updates - You can check the version installed in your vehicle, under Menu (the faceplate button) > Setup > Software Update. The website also provides clear instructions how to download and perform the software update using a USB flash drive (a dealer can do this for you, but I was quoted over $200 at Toyota Service, I opted to learn and do it myself.) My current configuration: iPhone 16
Replies
Boosts
Views
Activity
Jan ’25
Reply to LLDB RPC server crash in Xcode 16.3
Same here: lldb started crashing with simulator on encountering breakpoints, as of right now it even seems to crash reliably after some time. It seems to work properly on physical device Sequoia 15.4, XCode 16.2, iPhone 16 pro simulator 18.2 If that matters: I use github copilot xcode extension and that one also has issues => chat assistant crashes a lot and forces me to relaunch xcode every couple requests report.txt
Replies
Boosts
Views
Activity
May ’25
Reply to XCode 16 RC and Sequoia 15 RC - Running a XCTest UI test runs the test but does not open the simulator and initiating a record just hangs and never runs
@DTS Engineer Not OP but I am also seeing this issue on Xcode 16.0 (16A242d). I am attempting to run a test to an iPhone 16 Pro/18.0 sim and as @hogman78 said, sim never launches and test runner just hangs. Sim opens fine running & building, but not for UI tests. Tried resetting device (device > erase...) and building to something different, same behavior. Restarted MBP, no change. Sequoia 15.0
Replies
Boosts
Views
Activity
Sep ’24
Reply to MKMapView appears red on iOS 18 simulator + Xcode 16
I've had the same problem for a while now. I am currently using Xcode version 16.2 (16C5032a). The problem is with the iOS 18.2 and iPhone 16 Pro Max simulator. Not with the iPhone 15 Pro Max Simulator and iOS 17.5. I can also zoom up to 24 meters and the colors remain the same. The problem starts at a zoom range of 1500 meters and not everywhere. Play around with the coordinates from the simulator. It works in Cupertino, San Francisco or other large cities, but not in rural areas. In Europe, the colors are red almost everywhere when zooming.
Replies
Boosts
Views
Activity
Jan ’25
Reply to Can't install any apps on my new iPhone 16 Pro with iOS 18 from XCode
I was running into the same error with my newly acquired iPhone 16 Pro. I downloaded Xcode 16.1 beta 2 and successfully set it up for development. This morning my phone was updated to what appears to be the final iOS 18 version (as opposed to the version installed on new phones) and tried Xcode 16 (NON beta) again. This time the setup for development worked immediately. That suggests to me that Xcode 16 came with a package specifically for the final version of iOS 18, and not for the version shipped on new phones. Hopefully this will all be resolved soon between shipping phones with the latest OS version and updates to Xcode. FWIW, I updated my phone manually in Settings>General>Software Update.
Replies
Boosts
Views
Activity
Sep ’24
Reply to iPhone 16 Pro - iOS 18 camera crashing
UPDATED: I forgot to mention that I am not running a beta, this is the gold release that has this issue (But I feel like its a beta) and I only singed into the dev side to see if a beta might have the fix for this. I agree, it should be raised as a bug. But I also think this should have never been a bug with a new phone pro model that always focuses on the camera. I’ve had his issue also, along with photos not displaying correctly when I look at them from the camera app, videos recording without now sound. And in a time I needed it to work and document damage from the storm for insurance reason. At the price of a iPhone 16 pro max this was a big failure.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
Oct ’24
Reply to .contactAccessPicker shows blank sheet on iOS 26.1
Thank you! I’ve tested the sample project on several devices running iOS 26.1 (iPhone 16 Pro) and iOS 18.6 (iPhone 11). On the iPhone 11, both AddContactButton and QuickAddContactButton work as expected - I’m able to add new contacts to the Contact List. However, on the device running iOS 26.1, tapping AddContactButton opens a blank sheet (see attached screenshot). In the Quick-Add section, after pressing the 'View' button, the debugger shows the following message: #ContactsButton response after touch -- encountered an error: Button is occluded
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Nov ’25
Reply to NSCocoaErrorDomain Code=513 after user delete's
I can't reproduce the issue you described by building the sample app with Xcode 26.0 beta 5 (17A5295f) and running it on my iPhone 16 Pro + iOS 18.6.1 – After deleting the app's iCloud data with Settings, and going back to the sample app, I see that the documents I created disappears, and can create a new document without any error. What system version did you test with? I am wondering if the issue only occurs on an old system version... Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Aug ’25
iPhone 16 pro max ios 26 beta 2 lagging in animation while closing folder and while closing assistive touch button
iphone 16pro max lag in animation while closing an app folder on my home screen and while closing assistive touch button . The animation after closing is like the folder is still open for Seconds and assistive touch button all buttons are showing for seconds even after closing it
Replies
0
Boosts
0
Views
45
Activity
Oct ’25
Reply to Cannot run Animation Hitches Instrument
I see the same problem whenever I profile on a physical iOS device from Xcode 16.1 or 16.2 Beta 2 with any instrument using a recording mode of “deferred” (which happens to be the default recording mode for the Hitches tool). If I change the recording mode to “Capture last n seconds” (or, when available, “Immediate”), the errors do not appear. FWIW, my configuration is similar: M1 Mac Studio, Sequoia 15.1. Profiling a new blank project on iPhone 16 Pro Max, iOS 18.1.
Replies
Boosts
Views
Activity
Nov ’24
Reply to Callkit call blocking problem
In my case, when I try to block calls on iOS 26, the blocking doesn't occur; the scenarios seem intermittent. If I create two CallDirectory extensions, the first blocks the numbers, but the second doesn't. Interestingly, the extension marks the number as suspicious. There's also a case where, on iOS 26 on an iPhone 16 Pro, the functionality doesn't work at all. I'd like to know if there have been any changes to the use of CallKit in iOS 26, because users of my app on iOS 18 and below report successful blocking.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Nov ’25
Reply to Sharing data between Targets via App groups but Userdefault Container is null
Main app bundle identifier: in.xxx.app Intent extension identifier: in.xxx.app.MuteIntent App group: group.in.xxxx.shared I have save value A in Main App target and B in Intent extension target against the same key and re-run the app. Both target have its own value which I saved previously. It means UserDefaults in not shared between targets. Also tested same behaviour with Message extension where UserDefaults sharing working fine. xcode: 16.2 iOS simulator: iphone 16 pro 18.1 Is it limitation with Intent extension (Siri)?
Replies
Boosts
Views
Activity
Feb ’25
Reply to Regression: Heavy Delay of Push Notifications on iOS 18.1 beta (10s and more)
This delay still occurs in iOS 18.1 RC (22B82) on iPhone 16 Pro when Apple Intelligence is enabled. This is an unacceptable amount of delay for time sensitive notifications, for example - push notifications from the Duo MFA application do not appear until 10-12 seconds, and the time out to response is only 20-30 seconds. I filed my own feedback fro this under FB15418918, which reports More than 10 similar reports. The only solution I've found is to completely disable Apple Intelligence.
Replies
Boosts
Views
Activity
Oct ’24
Reply to The iOS 26 simulator crashed due to NWPathMonitor
I was able to reproduce this as follows: Using Xcode 26.0 beta on macOS 15.5, I created a new project from the iOS > App template. I replaced ContentView.swift with the code you posted. I set the app’s deployment target to iOS 16. I ran the app on the iPhone 16 Pro / iOS 26 simulator. I suspect that you’re hitting the issue discussed on this thread. As suggested on that thread, I was able to work around this by adding this code to my App struct: struct Test789304App: App { init() { _ = nw_tls_create_options() } … } Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
Jun ’25
Reply to After building the project, the search form does not allow typing, but pasting works.
The warnings you see are caused by Apple's code, not yours. It relates to displaying a keyboard, so you can ignore those. Just tried this here and it works fine. iPhone 16 Pro Max 18.2 Simulator. What happens if you click in the text field in your app in the Simulator, and press Cmd+K to toggle the software keyboard? Does it let you type into the field? Can you remove/comment out the .overlay that contains the clear button with image xmark.circle.fill. Maybe the tap onto the field is being intercepted by the Spacer() and that image? I don't know, I'm just trying to see what might cause your issue.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Feb ’25