“iPhone 16 pro”

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.

I'm encountering an issue while trying to build my iOS app in Xcode for the simulator. Issue: Xcode Version: 15.x macOS Version: 14.x (Sonoma) Simulator: iPhone 16 Pro Error Message: Command ClangStatCache failed with a nonzero exit code Steps Taken: Cleaned build folder (Shift + Cmd + K) Deleted DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData) Updated Xcode and checked iOS SDK updates Disabled Clang Static Analyzer Cache None of these steps resolved the issue. Any help would be appreciated! Thanks in advance.

Having the same problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. Worth noting that I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far, at least the case of the 16 Pro / U2 / iOS 26 (?): 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Placing both a 16 Pro and a 12 face down on a table with rear cameras covered: 12 continues t

Hello, This is a follow-up to my previous report. We have identified reliable steps to reproduce the issue. We have set up a test page with a standard tag. Since this problem occurs without any external libraries, so this problem seems to be with the native HLS player in iOS. Steps to Reproduce: Open the test page in Safari. Play the video, seek to a different position, and then pause it. Switch to another browser tab. (If the issue doesn't occur, switch back to the video tab, wait a few seconds, and then switch away again.) Environment: Device: iPhone 16 Pro. OS: iOS 18.5 Thank you for looking into this. We hope this issue will be addressed in an upcoming release. Best regards, Kazutoshi-Iso

Thanks for your reply, sorry for the delay for some reason the alert wasn't enabled for replies despite being the author, I have enabled it now and will try to remember to do that for all my future posts. That's strange you can't reproduce. I can confirm the issue also exists on iOS 18.3.1 device and iOS 18.4 Beta simulator. 18.3.1 test: Xcode Version 16.2 (16C5032a) iOS min deployment 18.2 Swift 5 Language Version Deployed to device: iPhone 14 Pro, iOS 18.3.1 18.4 beta test: Xcode Version 16.3 beta (16E5104o) iOS min deployment 18.4 Swift 5 Language Version Deployed to simulator: iPhone 16 Pro, iOS 18.4 (22E5200m) Just to confirm how to test: the list rows and the sheet are expected to automatically disappear. But only the rows do, i.e. ends up like this:

I'm also seeing this using Xcode 26 beta 2 and an iPhone 16 Pro Max on iOS 26 beta 3. In a demo chat app project, the error is thrown for roughly half of prompts. Often trying the same prompt multiple times will succeed or fail at random. It reliably happens when using the FoundationModelsTripPlanner sample code. Every attempt to generate an itinerary throws an error: The operation couldn’t be completed. (FoundationModels.LanguageModelSession.GenerationError error 2.) Printing description of error: ▿ GenerationError ▿ guardrailViolation : Context - debugDescription : May contain sensitive or unsafe content ▿ underlyingErrors : 1 element ▿ 0 : GenerationError ▿ guardrailViolation : Context - debugDescription : May contain unsafe content - underlyingErrors : 0 elements

Hello, while creating the sample app I found a message in the debugger: Widget archival failed due to image being too large [1] - (6000, 4000), totalArea: 24000000 > max[2121055.200000]. Can you provide a table, what is the limit or how to calculate it? I found that this limit is different for all my devices. Now I use a magic number = 3.6. It is not the scale of the device screen, but something else. //ipad 10 sqrt(13.54) ~ sqrt(13) ~ 3.6 //iphone 16 pro sqrt(18.5) ~ 4.3 //iphone SE sqrt(17.59) ~ 4.1 And it is better to have documentation about it. And the archiving of images in the widget is not very fast. Especially it becomes a problem when using a long timeline. Even if the image is the same for all parts of the timeline, archiving is slow.

Hello. I am having the same problem with the same symptoms with an application I am releasing. Does anyone know the cause or solution? The situation is as follows. It occurs when I try to play a FairPlay video. Error Domain=NSURLErrorDomain Code=-1008 See -[AVPlayerItem errorLog] for 2 events UserInfo={NSDebugDescription=See -[AVPlayerItem errorLog] for 2 events, NSLocalizedDescription=リソースは利用できません, NSUnderlyingError=0x303fe8630 {Error Domain=CoreMediaErrorDomain Code=-12884 (null)}} This error does not occur for all users, only for some. The device used by the user that is experiencing this is an iPhone 16 Pro (18.2.1). The error seems to occur before accessing the license server. Thank you in advance for your support!

Thanks for the reply. While that may be true, for you. I cannot login to outlook.com on Edge, Safari or Chrome. All those browsers want me to login to my Microsoft account or sync my setting. Upon clicking on and trying to login to my account on Safari or Chrome the screen goes blank, never to recover. When I try on Edge, it want me to use the Authenticator, which of course I cannot do either because it wants me to setup my account, which I cannot do because it will not log me in due to too many attempts. I cannot login to outlook.com nor any Microsoft address without first logging in to my account. It's a vicious loop of going no where. Anything associated with Microsoft on my phone is fubar'd. No Word, no Excel, no Outlook or anything associated with my account/syncs are possible. This issue is only on my iPhone 16 Pro! My iPad running 17.7 has no issues! Something must have gotten glitched with my Microsoft account when transferring my data for 13 Pro to 16 Pro

Having a similar problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far: 16 Pro / U2 / iOS 26 (?) 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Seems to start an NI session with dirSrc as 'none' and then resolves to 'hAngle' after camera convergence is complete 12 / U1 / iOS 18 Seems to start an N

I was just in the same boat but was able to boot into DFU mode to resolve it. I was running the latest 18.5 beta on my iPhone 16 Pro Max. Decided to try the iOS 26 dev beta (like I do every year) and encountered my first soft brick situation...got stuck on the battery splash as described here. Putting the device in DFU mode (direct firmware update) allowed me to restore using my Mac. Keep in mind this will wipe your device, but I'm an iCloud user so not worried about that, and using my phone in general was most important to me. 9to5 Mac has a pretty good article on using DFU mode. Keep in mind when done right, you will not see an Apple logo or any splash, you'll see a black screen. Then when plugging into your Mac it will be recognized (unlike with the battery splash). Good Luck.

I've reproduced this on these 2 setups using the same iCloud account: Xcode 26.0 beta 4 (17A5285i) & iPhone 12 running iOS 26.0 (23A5326a) Xcode 16.4 (16F6) & iPhone 16 Pro running iOS 18.6.1 (22G90) Deleting the iCloud data for the app from one device also allows me to reproduce the issue on the other device. The error printed in the sample project by the console is: You don’t have permission to save the file “Documents” in the folder “iCloud~com~hfriia~SimpleiCloudDocument1”. Failed to save a document! I just tested on this setup using another iCloud account and it functions as expected - I can immediately recreate the documents folder and save a document: Xcode 26.0 beta 4 (17A5285i) & iPhone 7 running iOS 15.8.4 (19H390) Xcode 26.0 beta 4 (17A5285i) & iPhone XR running iOS 18.6.1 (22G90) Maybe there's something wrong with the first iCloud account?