“Xcode”

Update: I've had a chance to speak with an Apple build-tools engineer and was told that this is intentional after all. There are certain app-validation tools that have not yet been updated to support static frameworks. These tools would reject apps with frameworks that do not contain binaries, and therefore, at least for now, Xcode does add this stub on purpose.

The same problem on Xcode 26.3 NSInternalInconsistencyException event dispatch <_MPRemoteCommandEventDispatch: sourceID=SenderDevice = , SenderBundleIdentifier = , SenderPID = <9154> ((null))> state:201> deallocated without calling continuation userInfo: { NSAssertFile = _MPRemoteCommandEventDispatch.m; NSAssertLine = 39; } Crashed: Thread 0 CoreFoundation __exceptionPreprocess + 164 1 libobjc.A.dylib objc_exception_throw + 88 2 Foundation _userInfoForFileAndLine + 0 3 MediaPlayer -[_MPRemoteCommandEventDispatch dealloc] + 144 4 CoreFoundation -[__NSArrayI_Transfer dealloc] + 84 5 libobjc.A.dylib AutoreleasePoolPage::releaseUntil(objc_object**) + 204 6 libobjc.A.dylib objc_autoreleasePoolPop + 244 7 CoreFoundation _CFAutoreleasePoolPop + 32 8 CoreFoundation __CFRunLoopPerCalloutARPEnd + 48 9 CoreFoundation __CFRunLoopRun + 1976 10 CoreFoundation _CFRunLoopRunSpecificWithOptions + 532 11 GraphicsServices GSEventRunModal + 120 12 UIKitCore -[UIApplication _run] + 792 13 UIKitCore UIAppl

[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you

[quote='880225022, wu_aaron, /thread/818708?answerId=880225022#880225022, /profile/wu_aaron'] we need to establish multiple additional NWConnection instances … over the Wi‑Fi Aware network [/quote] I don’t think you can do this on currently shipping systems. However, we’ve added support for it in iOS 26.4 beta. This is sufficiently ‘bleeding edge’ that the docs haven’t hit the Developer website yet. But the APIs are in the iOS 26.4 beta SDK (I’m using Xcode 26.4b3, build 17E5179g) and there’s documentation in Xcode itself. To set up a listener: let devices: WAPublisherListener.Devices = … specific devices … let listener = try NetworkListener(for: .wifiAware(.addingConnections(from: devices)), using: .parameters({ TCP() }).localPort(12345)) On the client side, do this: let connection: NetworkConnection = … original connection … guard let wifiAwareEndpoint = connection.currentPath?.remoteEndpoint?.wifiAware(port: 12345) else { // … handle the failure … } // … connect to that endpoint … If you

There is no approval process for creating an NE packet tunnel provider [1]. Any paid developer can do that [2]. Why do you think that such an approval is necessary? If you’re using Xcode, you should be able to add the Network Extension capability to your app and appex, check the Packet Tunnel box, and let its automatic code signing handle the rest. But you’re the second person to ask a question like this recently [3], suggesting that something is misleading folks. I’d like to find that and fix it. ps Some NE providers have deployment restrictions. See TN3134 Network Extension provider deployment for the details. Also, don’t try to use a packet tunnel provider for something other than VPN. See TN3120 Expected use cases for Network Extension packet tunnel providers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Other than approval to join the Apple Developer Program itself. [2] That wasn’t always the case. See Network Extension

Some more hints and tips in this space: The easiest way to determine the actual calling conventions for a given function is to create a small project in Xcode that calls the function and then looking at the resulting assembly. The Product > Perform Action > Assemble command is super helpful in that case. But you can also run the program and choose Debug > Debug Workflow > Always Show Disassembly [1]. Apple documents its calling conventions in Xcode > Application binary interfaces. This is basically Arm’s Procedure Call Standard with a few tweaks. And one of this tweaks affects varags. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It says something about me that I have a hot key for that (-:

It sounds like your static library isn't built as an XCFramework that then contains your static library. In essence, your library needs to be built twice, once for iOS devices and a second time for iOS simulators, with both copies and the header files then packed inside of the XCFramework so Xcode then handles all of the details from there. The documentation covers all of the details you need. — Ed Ford,  DTS Engineer

Thank you for your post. Have you also considered reaching out to the React Native support channel to explore the support resources provided by third-party software developers to obtain assistance with their applications. I highly recommend utilizing Xcode to create a native project. This approach allows you to utilize your subscriptions and purchases through StoreKit, as outlined in the documentation provided by the Apple App Store Commerce Engineer in the previous post. Albert Pascual
  Worldwide Developer Relations.

Hi @DTS Engineer , I am also facing this weird issue I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info. Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the Generate dSYM phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The

I filed a bug report with an sample project and 2 files for testing. I confirm the problem. FB22253128 Here the message in FB (with the zipped sample project and 2 test files): Context: Xcode 26.3, iOS 18.7.6 on iPhone Xs In this iOS app, I call UIActivityViewController to let user Airdrop files from the app. When trying to send a URL whose file name contains some characters like accentuated (-, é, '), the transfer fails. Removing those characters makes it work without problem. Steps to reproduce Build and load the app on iPhone transfer the 2 pdf files ('name accentué.pdf' and 'name plain.pdf' to the Documents folder of Test app (I did it in Finder on Mac with iPhone USB connected to the Mac). The 2 files are identical except their name. Run the app Tap 'Send by AirDrop name plain.pdf' and select AirDrop to Mac : Transfer OK Tap 'Send by AirDrop name accentué.pdf' and select AirDrop to Mac : Transfer fails

Thanks for sharing the result of your tests. To comment: With Xcode debugger attached: HR sampling worked great (~5 second intervals), continuous and stable This is as-designed: In the case where your app is attached to the Xcode debugger, the debugger will keep the attached app alive to maintain the debugging session. I am glad that you called this out, which gives me a chance to clarify. Pressing the Crown navigates away and HR sampling stops immediately For a sleep app, users will inevitably press this accidentally while napping This behavior is as-designed as well, and is documented in Taking advantage of frontmost app state. To quote: If a person explicitly closes the app by pressing the digital crown or covering the screen, the app doesn’t become the frontmost app and doesn’t remain in the inactive state, but transitions quickly to the background instead. (The app will then become suspended after transitions to the background.) The app was terminated by the system within ~10 minutes, e