“Xcode”

Thanks for this interesting post! I'm not an expert on that field nor that API. Hope one of the engineers on that team can jump into this thread for better info. These specific FigXPCUtilities and FigCaptureSourceRemote logs are almost certainly benign internal framework noise rather than a regression or a flaw in your capture pipeline. Looking up the err=-17281 is a CoreMedia error code that, without knowing here, typically points to a minor XPC synchronization hiccup, a port invalidation, or an asynchronous state mismatch during the setup or teardown of the capture session? I believe this logs are for information only and should be removed. Code paths that silently recovered in older iOS versions often have their log levels elevated in newer releases (or beta releases), resulting in console spam. If your AVCaptureVideoDataOutputSampleBufferDelegate is successfully receiving CMSampleBuffer frames and your preview layer is rendering smoothly. You can safely ignore these logs. If you want to temporarily hide t

@AlkensoDev I would recommend to file a bug because I'm unable to reproduce it on the latest release of Xcode. I would also recommend when filing the bug to provide your sysdiagnose as maybe could be something on the set up of your environment. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

Hello - Additional troubleshooting tips for testing IAP and product(s) availability in Xcode and in Sandbox can be found in the linked pages. Please let us know if you have any other questions. Thank you.

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.