build disappears

Is there a workaround, unofficial method, or private API to generate a local hotspot from an app on iOS, similar to what can be done on Android? No APIs exist that will allow an app to turn the iOS device into a hotspot. Are there any best practices for improving the local Wi-Fi connection experience between an accessory and an iPhone in the absence of hotspot controls? We have a range of APIs an app can use to have the iPhone connect to a specific hotspot. In a modern app, that flow starts by pairing with your Wi-Fi accessory using AccessorySetupKit, then using either NEHotspotManager or our Wi-Fi aware support to actually join that hotspot. Note that while the AccessorySetupKit documentation is primarily focused on Bluetooth, that's largely because the Bluetooth process is significantly more complicated than the Wi-Fi flow. Is there an alternative within the MFi program? Nothing* in the MFi program applies to your particular situation. We do license WAC (Wireless Accessory Configuration) through the MFi pro

We have a management application which manages security enable and disable for an external PCIe-based storage device using Kernel Extension (SCSI Architecture Model Family for External USB Mass Storage devices which deals with IOSCSIBlockCommandsDevice, IOSCSIPeripheralDeviceType00 and IOBlockStorageService). FYI, KEXT support has been deprecated for several years and replaced by DriverKit. In your case, that would probably mean building on SCSIPeripheralsDriverKit. If you haven't already, I'd strongly recommend that you begin working on that transition as soon as possible. Now the issue we are facing is when we try to unlock the device using security code (already being set), we will relink the device using VU command (RelinkBridge). Even though both the commands are successful, the device is not getting relinked due to which we are not able to use the device for storage. I'm not aware of any issue in the system that would cause what you're describing. Your KEXT has final control over what your devi

We have this issue too. How can our iOS engineering team do their jobs without access to testflight if we adopt managed apple ids? The only reference on the topic is here: https://support.apple.com/guide/apple-business-essentials/service-access-with-managed-apple-accounts-axm171b3ee95/web which cites privacy concerns as a nebulous non-reason. Our teams that own mobile software need to use testflight to test release-track builds.

I find the reason of this problem, in Xcode 26, when you download the simulator, the default iOS 26 simulator's arch is arm64, so when you add the Excluded Architectures arm64, the build result get none of any arch. The solution is to download the universal simulator, first, you should delete the iOS 26 simulator, then run xcodebuild -downloadPlatform iOS -architectureVariant universal in terminal, then xcode can download the universal of iOS 26 simulator.

As a followup - after upgrading to Unity 6000.2.6f1, these errors seem to have disappeared. If you're running into these issues on an earlier Editor version, try upgrading if you can.

Hello, We don't have specific points of the app code where it may be crashing, since it's random, we already seen code crashing at very different locations around the app. Currently, about 5% of our users base is having this crash, also another detail, we are seeing this around different versions of iOS, not specific to iOS 18 or 26. We suspected at first about the compiler of new Xcode 26 (since this was the first version compiled with new Xcode), but it seems it is not that. We have sent a new build out today, compiled with Xcode 16.4, but no luck, still crashes. I'm attaching 2 screenshots, from the crashing stacktrace, one from Sentry and the other one from Xcode crash reporter directly. Also, attached the .crash file with the full stacktrace that can be found at Xcode. 2025-10-01_14-37-42.7083_-0500-2937c5ddef763873e9e26e42e243231a23e27df5.crash

On which version of Xcode do you build ? Have you the list of all libraries you use ? Finally, have you accepted the eventual Xcode message (appear in left panel) to update to new settings ? Old thread, but you may find interesting hints to look at: https://stackoverflow.com/questions/48501857/non-public-api-usage-the-app-contains-one-or-more-corrupted-binaries