Search results for

iPhone 16 pro

78,789 results found

Post

Replies

Boosts

Views

Activity

Reply to Slow incremental build times with xcodebuild command
I ran some tests and can confirm that with Xcode 26, xcodebuild now works just as fast as Xcode 16 with the workaround. This is true both when rebuilding the app without any changes and when performing incremental builds after making changes. I also noticed that Xcode 26 no longer calls the slow developerservices2.apple.com. Instead, it uses https://ocsp2.apple.com, which is much faster.
3w
ContentDelivery 409 “corrupted binaries”
Builds rejected with generic ContentDelivery 409 “corrupted binaries” (no email, no Activity entry) App ID: 6752832930 Bundle ID: com.taleway.tw Toolchain: Xcode 16.0 (build 24319) on macOS 15.6.1 (24G90) What happens Archiving (Release, manual signing) succeeds. Upload/validation via Xcode Organizer or xcrun altool immediately fails with: Validation failed (409) The app contains one or more corrupted binaries. Rebuild the app and resubmit. (ID: ef414ced-bf4e-40a6-8f5f-d4ba744c9433) altool also reports a preceding 500 “internal server error” (L4JS7YJVZYJMHBI4ISC4L3UQBM) before the 409. No system-generated email ever arrives (nothing under App Store Connect → Activity). We therefore have no specific error message or file name to fix. What we’ve checked Archive entitlements and embedded provisioning profiles match: App entitlements: CarPlay audio, App Group group.com.taleway.tw, get-task-allow=false. Intents extension entitlements: com.taleway.tw.TWIntents, get-task-allow=false. Profiles decoded via openssl smi
0
0
76
3w
Reply to Xcode 16 compatibility with newly-released devices
Thanks for your post. Please check the version of iOS Xcode 16 supports https://developer.apple.com/documentation/xcode-release-notes/xcode-16-release-notes and what version of iOS the new iPhone 17 comes out with. Latest version of Xcode 16.4 release notes: https://developer.apple.com/documentation/xcode-release-notes/xcode-16_4-release-notes Albert Pascual
  Worldwide Developer Relations.
3w
Reply to peer-to-peer networking for iOS, iPadOS, watchOS, tvOS
Dear Eskimo1 , I do not understand your response (Nov'24) : Nope. Multipeer Connectivity hasn’t used Bluetooth since… . In the documentation: [https://developer.apple.com/documentation/multipeerconnectivity], in the overview, we can read: In iOS, the framework uses infrastructure Wi-Fi networks, peer-to-peer Wi-Fi, and Bluetooth personal area networks for the underlying transport. In macOS and tvOS, it uses infrastructure Wi-Fi, peer-to-peer Wi-Fi, and Ethernet. I am currently starting to write a new app, running on the iPhones, trying to communicate between them (peer to peer). Result: When the iPhones have wifi enabled, bonjour services work as expected (probably not peer to peer). when I turn wifi off on the iPhones, Bonjour does not work (no connection happens). So I would like to know if your statement on the non existance of MC on Bluetooth is confirmed and therefore how do we need to read the sentences in the documentation. Thank you very much
3w
Macos26 Tahoé is Hell with "Relocated Items"
I just discover that feature (a folder lost in the middle of others desktop folder ). so with each updates: -/usr/local is emptied -somes apps in the Application folder, are deleted, even paid apps .. -i lost : Docker, python 3.13, latexlive2025, Apache NetBeans, java install, Affinity Publisher 2, all my 3D slicers ... github desktop, Epic Games Launcher, ........ 296go of apps Franckly : c'est la merde !!! I am using a MacBook Pro 16 2019 any way to stop this behavior ? thank you !!!
Topic: Design SubTopic: General
0
0
646
3w
Reply to iPhone17 bluetooth background scanning issue
This is likely due to the state of the specific device you are observing the issue rather than an iPhone 17 or iOS 26 issue. When apps are in the background, the scanning slows down in stages, and the advertising interval of the peripheral is critical to being able to discover and connect. Please do check what the advertising interval is. We recommend 20 ms, 152.5 ms, 211.25 ms, 318.75 ms, 417.5 ms, 546.25 ms, 760 ms, 852.5 ms, 1022.5 ms, 1285 ms intervals. Even with these specific intervals, using the slower ones, discovery can take up to several minutes. So, I would believe the issue is not scanning is being stopped, but slowing down so you might be thinking it has stopped. You can test this by changing the advertising interval of the peripheral to 20 ms, and then it should be discovered in seconds even if your app is in the background. Argun Tekant /  WWDR Engineering / Core Technologies
Topic: App & System Services SubTopic: Core OS Tags:
3w
Reply to Canvas Preview: Cannot preview in this file
On my Mac mini M4 Pro, I’ve installed macOS Tahoe 26.0 and Xcode 26.0.1. The error message still appears, even when testing with the iPhone 17 Pro and iPad Pro 11-inch M4 simulators. The FB numer is: FB20362054 == PREVIEW UPDATE ERROR: GroupRecordingError Error encountered during update group #19 ================================== | FailedToLaunchAppError: Failed to launch net.thomasbayer.ChatPrototype | | ================================== | | | [Remote] JITError | | | | ================================== | | | | | [Remote] CouldNotLoadInputObjectFile: Could not load object file during preview: /Users/thomas/Library/Developer/Xcode/DerivedData/ChatPrototype-ebbbmisjgapzykawaadxudtxyjmg/Build/Intermediates.noindex/ChatPrototype.build/Debug-iphonesimulator/ChatPrototype.build/Objects-normal/arm64/ChatPrototypeApp.o | | | | | | path: /Users/thomas/Library/Developer/Xcode/DerivedData/ChatPrototype-ebbbmisjgapzykawaadxudtxyjmg/Build/Intermediates.noindex/ChatPrototype.build/Deb
Topic: UI Frameworks SubTopic: SwiftUI
3w
Safari App crashes when running with Safari extension intermittently
I have observed Safari App starts crashing when running with my safari extension. Our Safari extension polls the host app every 60s. The extension receives and completes requests in func beginRequest(with context: NSExtensionContext) (we always call context.completeRequest(...)). The crash is intermittent: beginRequest itself does not throw. Looking for guidance about likely causes. I am attaching the snippet from crash report. Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace RUNNINGBOARD, Code 3490524077 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x1856f5c34 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x1857083a0 mach_msg2_internal + 76 2 libsystem_kernel.dylib 0x1856fe764 mach_msg_overwrite + 484 3 libsystem_kernel.dylib 0x1856f5fa8 mach_msg + 24 4 CoreFoundation 0x185822cbc __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x1858215d8 __CFRu
2
0
346
3w
Clarification on Data Collection in CallerId App
Hello everyone, Our app, NumberBox, was rejected due to Guideline 5.1.1, with the review team saying it “collects information from public sources to build individual profiles.” We want to clarify: All data is 100% user-reported. Users voluntarily submit phone numbers (spam, scam, or telemarketing) and assign tags through the “Add Tag” feature. No data is collected from public sources or user contacts. No profiles are built automatically. All user submissions are reviewed by our support team before being displayed. The sole purpose of NumberBox is to help users avoid unwanted or scam calls, not to collect personal data. Our updated Privacy Policy is here: https://numberbox.app/privacypolicy Has anyone encountered a similar issue with Guideline 5.1.1? Any guidance on how to clearly communicate this to App Review would be greatly appreciated. Thanks in advance!
1
0
95
3w
SCStreamUpdateFrameContentRect X coordinate always returns 48 instead of expected 0
SCStreamUpdateFrameContentRect X coordinate always returns 48 instead of expected 0 Environment Device: MacBook Pro 13-inch macOS: Sequoia 15.6.1 Xcode: 16.4 Framework: Screen Capture Kit Issue Description I'm experiencing an unexpected behavior with Screen Capture Kit where the SCStreamUpdateFrameContentRect X coordinate consistently returns 48 instead of the expected 0. Code Context I'm using SCContentSharingPicker to capture screen content and implementing the SCStreamOutput protocol to receive frame data. In my stream(_:didOutputSampleBuffer:of:) method, I'm extracting the content rect information from the sample buffer attachments: func stream(_ stream: SCStream, didOutputSampleBuffer sampleBuffer: CMSampleBuffer, of type: SCStreamOutputType) { switch type { case .screen: guard let attachmentsArray = CMSampleBufferGetSampleAttachmentsArray(sampleBuffer, createIfNecessary: false) as? [[SCStreamFrameInfo: Any]] else { return } guard let attachments = attachmentsArray.first else { return } if !atta
1
0
44
3w