Search results for

“iPhone 16 pro”

80,726 results found

Post

Replies

Boosts

Views

Activity

Reply to Apple watch Xcode pairing & connection issues
Same issue for me as well and my ability to test on a real device is totally blocked and has been actually since some time back in Nov.! Xcode 26.3 iOS 26.3.1 watchOS 26.3 Watch was paired to Xcode but would never connect due to the same tunneling errors mentioned by others. After unpairing via Xcode Devices and Simulators the watch cannot be repaired even though I have unpaired and repaired it with iPhone and unpaired and repaired the iPhone to Xcode. NOTHING will cause Xcode to find the watch again. Damn it Apple this crap has been an ongoing issue since Xcode 26.0 How do you have 3 dot releases and not fix something like this?! Might have gotten the watch re-connected via another suggestion in higher up in this thread to connect mack to iPhone via Hotspot. I can see the watch again in Devices and Organizers, but the setup is taking foreeeeeevvverrr so not sure what happen when I switch the mac back to regular wifi.
2w
Someone help me, i need to connect to wifi by scan a qrCode in my Flutter APP
Hi, I'v got the error by using NEHotspotConfiguration to connect a wifi spot but get:NEHotspotConfigurationErrorDomain code=8. I hope to get the same result as when scanning the code with the system camera. A pop-up window will appear, and I just need to click Join to successfully connect. Here's the logs: [OneAppWifi][iOS] handleCheckWifiEnabled start (iOS 12+) [OneAppWifi][iOS] handleCheckWifiEnabled pathUpdateHandler status=satisfied [OneAppWifi][iOS] handleConnectWifi start, ssid=OPPO Find X6 Pro, pwd=len=16, authType=Optional(sae), hidden=false [OneAppWifi][iOS] handleConnectWifi cancelPendingConnection before new request ssid=OPPO Find X6 Pro [OneAppWifi][iOS] cancelPendingConnection called, errorCode=nil, currentSsid=nil [OneAppWifi][iOS] cancelPendingConnection silent cancel, just clear pendingConnectResult [OneAppWifi][iOS] handleConnectWifi apply completion with error, domain=NEHotspotConfigurationErrorDomain, code=8, userInfo=[NSLocalizedDescription: internal error.] [One
3
0
106
2w
Intermittent connectivity issues on iOS 26.4 Beta - Potential iCloud Private Relay conflict
I am investigating a connectivity issue reported by a user running latest iOS 26.4 Public Beta on an iPhone 17 Pro Max. Unfortunately, I am unable to reproduce this behavior on my end as I do not have access to an iPhone 17 Pro Max for testing, and my current devices do not exhibit the issue. However, the user's logs suggest a system-level networking issue : Symptoms: Flutter App (package dio): Requests fail with The connection errored: Failed host lookup: 'mydomain.com' Firebase SDK: Unable to fetch Firestore documents Duration: The outage is random, lasting between 5 to 15 minutes before self-resolving Scope: It affects both Wi-Fi and Cellular data By the way I found this report from another developer experiencing the exact same behavior: I run a mobile app that has millions of users. As of 1-2 weeks ago, we started getting reports that the app isn't working (failing to connect). It then goes back to connecting anywhere between 5 to 15-20 mins later. Every single one of t
1
0
172
2w
Reply to Potential Structural Swift Concurrency Issue: unsafeForcedSync called from Swift Concurrent context
I always had next console messages after first app hide (even in empty project): 0.5 Potential Structural Swift Concurrency Issue: unsafeForcedSync called from Swift Concurrent context. 0.5 Metadata: Process: TestError | Library: AXCoreUtilities | Subsystem: com.apple.Accessibility | Category: AXCommon I changed toggle on iPhone: Settings -> Accessibility -> Read & Speak -> Speak Selection (from ON to OFF) and messages disappeared. Hope it will help someone.
2w
Xcode 26 fails to load SPM packages
For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives Server SSH Fingerprint Failed to Verify as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?
7
0
884
1w
Swift Playgrounds Incompatibility with Xcode 16 Files and Swift Versions
I'm facing an issue with Swift Playgrounds and files created in Xcode 16. It seems that Swift Playgrounds does not support Swift 6, but even when I create files specifically with Swift 5, Swift Playgrounds still reports that the files are unsupported. This creates a significant problem because macOS Sequoia does not allow me to revert to Xcode 15, which might have offered better compatibility. As it stands, I can't find a solution to work seamlessly between Xcode and Swift Playgrounds. Has anyone else encountered this issue? Are there any workarounds or updates planned to address this compatibility gap? Any advice would be greatly appreciated!
6
0
1.2k
2w
Crashed: AXSpeech EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x000056f023efbeb0
Application is getting Crashed: AXSpeech EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x000056f023efbeb0 Crashed: AXSpeech 0 libobjc.A.dylib 0x4820 objc_msgSend + 32 1 libsystem_trace.dylib 0x6c34 _os_log_fmt_flatten_object + 116 2 libsystem_trace.dylib 0x5344 _os_log_impl_flatten_and_send + 1884 3 libsystem_trace.dylib 0x4bd0 _os_log + 152 4 libsystem_trace.dylib 0x9c48 _os_log_error_impl + 24 5 TextToSpeech 0xd0a8c _pcre2_xclass_8 6 TextToSpeech 0x3bc04 TTSSpeechUnitTestingMode 7 TextToSpeech 0x3f128 TTSSpeechUnitTestingMode 8 AXCoreUtilities 0xad38 -[NSArray(AXExtras) ax_flatMappedArrayUsingBlock:] + 204 9 TextToSpeech 0x3eb18 TTSSpeechUnitTestingMode 10 TextToSpeech 0x3c948 TTSSpeechUnitTestingMode 11 TextToSpeech 0x48824 AXAVSpeechSynthesisVoiceFromTTSSpeechVoice 12 TextToSpeech 0x49804 AXAVSpeechSynthesisVoiceFromTTSSpeechVoice 13 Foundation 0xf6064 __NSThreadPerformPerform + 264 14 CoreFoundation 0x37acc CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 28 15 CoreFoundation 0x36d48 __CFRunLoopDoSource0 +
4
0
1.5k
2w
AXSpeech Crash
I have a very terrible crash problem in my App when I use AVSpeechSynthesizer and I can't repetition it.Here is my code, It's a singleton- (void)stopSpeech { if ([self.synthesizer isPaused]) { return; } if ([self.synthesizer isSpeaking]) { BOOL isSpeech = [self.synthesizer stopSpeakingAtBoundary:AVSpeechBoundaryImmediate]; if (!isSpeech) { [self.synthesizer stopSpeakingAtBoundary:AVSpeechBoundaryWord]; } } self.stopBlock ? self.stopBlock() : nil; } -(AVSpeechSynthesizer *)synthesizer { if (!_synthesizer) { _synthesizer = [[AVSpeechSynthesizer alloc] init]; _synthesizer.delegate = self; } return _synthesizer; }When the user leaves the page, I call the stopSpeech method。Then I got a lot of crash messagesHere is a crash log:# Crashlytics - plaintext stacktrace downloaded by liweican at Mon, 13 May 2019 03:03:24 GMT # URL: https://fabric.io/youdao-dict/ios/apps/com.youdao.udictionary/issues/5a904ed88cb3c2fa63ad7ed3?time=last-thirty-days/sessions/b1747d91bafc4680ab0ca8e3a702c52c_DNE_0_v2 # Organization: zzz # Plat
1
0
2.5k
2w
Reply to In App Purchase Products
Thanks for your post and your question. If it were possible to restrict a user from downgrading an app, how would that impact the user experience at the App Store level? How would this be perceived by users? App Store policies and the iOS system design mandate that users have ultimate control over their subscriptions. If you are selling storage, you will likely be utilizing Auto-Renewable Subscriptions. Even if you hide the downgrade option inside your app's UI, the user can always go to their iPhone's Settings > Apple ID > Subscriptions and select a lower-tier plan. Because you cannot prevent the downgrade, I would recommend you to handle the scenario gracefully within your app's logic. I would recommend you to look at all the technical resources available to you to make sure the downgrade is possible including if you must create a new storage and move the existing data. However, your backend and app logic must still be prepared for the user to bypass your UI and downgrade via their Apple ID s
2w
Reply to Direction data not available with U2 chip (iPhone 15 Pro and iPhone 16 Pro) when using Murata SR040/SR150 accessory
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
2w
Direction data not available with U2 chip (iPhone 15 Pro and iPhone 16 Pro) when using Murata SR040/SR150 accessory
Hello, I am developing with the Nearby Interaction framework using third-party UWB accessories (Murata SR040/SR150). I observed a difference between U1-based and U2-based iPhones: iPhone 12 Pro (U1 chip) NINearbyObject.direction returns valid 3D vector (x, y, z). Distance and direction both work as expected. iPhone 15 Pro and iPhone 16 Pro (U2 chip) NINearbyObject.direction is always nil. Only distance is returned (around 0.35–0.40 m in my test). Effectively behaves as distance-only mode. Environment: Hardware: iPhone 12 Pro, iPhone 15 Pro iOS version: 18.5 Accessory: Murata UWB SR040 / SR150 App: Using NINearbyAccessoryConfiguration with BLE-based discovery Info.plist includes NSNearbyInteractionUsageDescription Camera assistance was tested both ON and OFF Expectation: I expected the U2 chip to behave consistently with U1, i.e. provide direction vectors when possible. Instead, on iPhone 15 Pro
4
0
423
2w
Reply to CGSetDisplayTransferByTable no longer working on macOS Tahoe
Once again, CGSetDisplayTransferByTable appears to be broken, but specifically for the latest Macs - the Neo, the M5 Pro and M5 Max. Happens on 26.3 and 26.4 beta4. Received multiple reports about this. Involved Macs were tested with multiple apps that rely on this, like BetterDisplay, MonitorControl and f.lux.
Topic: Graphics & Games SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
Reply to Submitting first subscription on version page
Hello - In reviewing your account, it appears that you were able to successfully resubmit your IAP product on March 16, 2026 with an app update - and both the app update and IAP product are now approved and live in the App Store. Please let us know if you need any further assistance. Thank you.
Replies
Boosts
Views
Activity
2w
Reply to what this error
I have the exact same issue, also I can install the newest build on my phone through TestFlight
Replies
Boosts
Views
Activity
2w
Reply to Unable to Verify App... again 😐
I am experiencing the same issue as last week too - I was able to sign apps this morning, now it stopped working. The team ID & everything stayed the same - but my iPhone complains that its Unable to Verify App. Is ppq.apple.com really up & running?
Replies
Boosts
Views
Activity
2w
Reply to Apple watch Xcode pairing & connection issues
Same issue for me as well and my ability to test on a real device is totally blocked and has been actually since some time back in Nov.! Xcode 26.3 iOS 26.3.1 watchOS 26.3 Watch was paired to Xcode but would never connect due to the same tunneling errors mentioned by others. After unpairing via Xcode Devices and Simulators the watch cannot be repaired even though I have unpaired and repaired it with iPhone and unpaired and repaired the iPhone to Xcode. NOTHING will cause Xcode to find the watch again. Damn it Apple this crap has been an ongoing issue since Xcode 26.0 How do you have 3 dot releases and not fix something like this?! Might have gotten the watch re-connected via another suggestion in higher up in this thread to connect mack to iPhone via Hotspot. I can see the watch again in Devices and Organizers, but the setup is taking foreeeeeevvverrr so not sure what happen when I switch the mac back to regular wifi.
Replies
Boosts
Views
Activity
2w
Someone help me, i need to connect to wifi by scan a qrCode in my Flutter APP
Hi, I'v got the error by using NEHotspotConfiguration to connect a wifi spot but get:NEHotspotConfigurationErrorDomain code=8. I hope to get the same result as when scanning the code with the system camera. A pop-up window will appear, and I just need to click Join to successfully connect. Here's the logs: [OneAppWifi][iOS] handleCheckWifiEnabled start (iOS 12+) [OneAppWifi][iOS] handleCheckWifiEnabled pathUpdateHandler status=satisfied [OneAppWifi][iOS] handleConnectWifi start, ssid=OPPO Find X6 Pro, pwd=len=16, authType=Optional(sae), hidden=false [OneAppWifi][iOS] handleConnectWifi cancelPendingConnection before new request ssid=OPPO Find X6 Pro [OneAppWifi][iOS] cancelPendingConnection called, errorCode=nil, currentSsid=nil [OneAppWifi][iOS] cancelPendingConnection silent cancel, just clear pendingConnectResult [OneAppWifi][iOS] handleConnectWifi apply completion with error, domain=NEHotspotConfigurationErrorDomain, code=8, userInfo=[NSLocalizedDescription: internal error.] [One
Replies
3
Boosts
0
Views
106
Activity
2w
Intermittent connectivity issues on iOS 26.4 Beta - Potential iCloud Private Relay conflict
I am investigating a connectivity issue reported by a user running latest iOS 26.4 Public Beta on an iPhone 17 Pro Max. Unfortunately, I am unable to reproduce this behavior on my end as I do not have access to an iPhone 17 Pro Max for testing, and my current devices do not exhibit the issue. However, the user's logs suggest a system-level networking issue : Symptoms: Flutter App (package dio): Requests fail with The connection errored: Failed host lookup: 'mydomain.com' Firebase SDK: Unable to fetch Firestore documents Duration: The outage is random, lasting between 5 to 15 minutes before self-resolving Scope: It affects both Wi-Fi and Cellular data By the way I found this report from another developer experiencing the exact same behavior: I run a mobile app that has millions of users. As of 1-2 weeks ago, we started getting reports that the app isn't working (failing to connect). It then goes back to connecting anywhere between 5 to 15-20 mins later. Every single one of t
Replies
1
Boosts
0
Views
172
Activity
2w
Reply to Potential Structural Swift Concurrency Issue: unsafeForcedSync called from Swift Concurrent context
I always had next console messages after first app hide (even in empty project): 0.5 Potential Structural Swift Concurrency Issue: unsafeForcedSync called from Swift Concurrent context. 0.5 Metadata: Process: TestError | Library: AXCoreUtilities | Subsystem: com.apple.Accessibility | Category: AXCommon I changed toggle on iPhone: Settings -> Accessibility -> Read & Speak -> Speak Selection (from ON to OFF) and messages disappeared. Hope it will help someone.
Replies
Boosts
Views
Activity
2w
Xcode 26 fails to load SPM packages
For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives Server SSH Fingerprint Failed to Verify as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?
Replies
7
Boosts
0
Views
884
Activity
1w
Swift Playgrounds Incompatibility with Xcode 16 Files and Swift Versions
I'm facing an issue with Swift Playgrounds and files created in Xcode 16. It seems that Swift Playgrounds does not support Swift 6, but even when I create files specifically with Swift 5, Swift Playgrounds still reports that the files are unsupported. This creates a significant problem because macOS Sequoia does not allow me to revert to Xcode 15, which might have offered better compatibility. As it stands, I can't find a solution to work seamlessly between Xcode and Swift Playgrounds. Has anyone else encountered this issue? Are there any workarounds or updates planned to address this compatibility gap? Any advice would be greatly appreciated!
Replies
6
Boosts
0
Views
1.2k
Activity
2w
Crashed: AXSpeech EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x000056f023efbeb0
Application is getting Crashed: AXSpeech EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x000056f023efbeb0 Crashed: AXSpeech 0 libobjc.A.dylib 0x4820 objc_msgSend + 32 1 libsystem_trace.dylib 0x6c34 _os_log_fmt_flatten_object + 116 2 libsystem_trace.dylib 0x5344 _os_log_impl_flatten_and_send + 1884 3 libsystem_trace.dylib 0x4bd0 _os_log + 152 4 libsystem_trace.dylib 0x9c48 _os_log_error_impl + 24 5 TextToSpeech 0xd0a8c _pcre2_xclass_8 6 TextToSpeech 0x3bc04 TTSSpeechUnitTestingMode 7 TextToSpeech 0x3f128 TTSSpeechUnitTestingMode 8 AXCoreUtilities 0xad38 -[NSArray(AXExtras) ax_flatMappedArrayUsingBlock:] + 204 9 TextToSpeech 0x3eb18 TTSSpeechUnitTestingMode 10 TextToSpeech 0x3c948 TTSSpeechUnitTestingMode 11 TextToSpeech 0x48824 AXAVSpeechSynthesisVoiceFromTTSSpeechVoice 12 TextToSpeech 0x49804 AXAVSpeechSynthesisVoiceFromTTSSpeechVoice 13 Foundation 0xf6064 __NSThreadPerformPerform + 264 14 CoreFoundation 0x37acc CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 28 15 CoreFoundation 0x36d48 __CFRunLoopDoSource0 +
Replies
4
Boosts
0
Views
1.5k
Activity
2w
AXSpeech Crash
I have a very terrible crash problem in my App when I use AVSpeechSynthesizer and I can't repetition it.Here is my code, It's a singleton- (void)stopSpeech { if ([self.synthesizer isPaused]) { return; } if ([self.synthesizer isSpeaking]) { BOOL isSpeech = [self.synthesizer stopSpeakingAtBoundary:AVSpeechBoundaryImmediate]; if (!isSpeech) { [self.synthesizer stopSpeakingAtBoundary:AVSpeechBoundaryWord]; } } self.stopBlock ? self.stopBlock() : nil; } -(AVSpeechSynthesizer *)synthesizer { if (!_synthesizer) { _synthesizer = [[AVSpeechSynthesizer alloc] init]; _synthesizer.delegate = self; } return _synthesizer; }When the user leaves the page, I call the stopSpeech method。Then I got a lot of crash messagesHere is a crash log:# Crashlytics - plaintext stacktrace downloaded by liweican at Mon, 13 May 2019 03:03:24 GMT # URL: https://fabric.io/youdao-dict/ios/apps/com.youdao.udictionary/issues/5a904ed88cb3c2fa63ad7ed3?time=last-thirty-days/sessions/b1747d91bafc4680ab0ca8e3a702c52c_DNE_0_v2 # Organization: zzz # Plat
Replies
1
Boosts
0
Views
2.5k
Activity
2w
Reply to In App Purchase Products
Thanks for your post and your question. If it were possible to restrict a user from downgrading an app, how would that impact the user experience at the App Store level? How would this be perceived by users? App Store policies and the iOS system design mandate that users have ultimate control over their subscriptions. If you are selling storage, you will likely be utilizing Auto-Renewable Subscriptions. Even if you hide the downgrade option inside your app's UI, the user can always go to their iPhone's Settings > Apple ID > Subscriptions and select a lower-tier plan. Because you cannot prevent the downgrade, I would recommend you to handle the scenario gracefully within your app's logic. I would recommend you to look at all the technical resources available to you to make sure the downgrade is possible including if you must create a new storage and move the existing data. However, your backend and app logic must still be prepared for the user to bypass your UI and downgrade via their Apple ID s
Replies
Boosts
Views
Activity
2w
Reply to Direction data not available with U2 chip (iPhone 15 Pro and iPhone 16 Pro) when using Murata SR040/SR150 accessory
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
Replies
Boosts
Views
Activity
2w
Direction data not available with U2 chip (iPhone 15 Pro and iPhone 16 Pro) when using Murata SR040/SR150 accessory
Hello, I am developing with the Nearby Interaction framework using third-party UWB accessories (Murata SR040/SR150). I observed a difference between U1-based and U2-based iPhones: iPhone 12 Pro (U1 chip) NINearbyObject.direction returns valid 3D vector (x, y, z). Distance and direction both work as expected. iPhone 15 Pro and iPhone 16 Pro (U2 chip) NINearbyObject.direction is always nil. Only distance is returned (around 0.35–0.40 m in my test). Effectively behaves as distance-only mode. Environment: Hardware: iPhone 12 Pro, iPhone 15 Pro iOS version: 18.5 Accessory: Murata UWB SR040 / SR150 App: Using NINearbyAccessoryConfiguration with BLE-based discovery Info.plist includes NSNearbyInteractionUsageDescription Camera assistance was tested both ON and OFF Expectation: I expected the U2 chip to behave consistently with U1, i.e. provide direction vectors when possible. Instead, on iPhone 15 Pro
Replies
4
Boosts
0
Views
423
Activity
2w