“build disappears”

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.

Same issue for me. The latest build I can see on my phone is from my 1.0 build. I cannot see my most recent, which is the first one in 1.0.1

[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 option cl

[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 option cl

Hi and thanks again for detailed response, First 10 was due to the information from Documentation/Conformance Test Outline.txt II.8 Shared Reply Timing The test tool issues a query for a shared (service PTR) record, and records how quickly the device answers. This test is repeated 10 times. So the assumption of this is understood and I agree to always have skewed binning. Attached below is a small test I threw together by pulling the response delay code out of mDNSResponder and then hard coding values Thank you for providing the code. I modify a bit to be able to build in our DUT // main.m // bonjour_ranTest // // Created by Kevin Elliott on 3/16/26. // #include #include #include #include // Added uint32_t mDNSPlatformRandomNumber(void) { return(arc4random()); } uint32_t mDNSRandom(uint32_t max) // Returns pseudo-random result from zero to max inclusive { #if 1 uint32_t ret = 0; uint32_t mask = 1; while (mask < max) mask = (mask << 1) | 1; do ret = mDNSPlatformRandomNumber() & mask;

Since you're asking about how to use Shortcuts with built-in system applications, you're best off asking about that in the Apple Support Community. The Apple Developer Forums are for questions about APIs and features intended specifically for developers, such as if you were trying to build your own app and have some of its functionality available for use by customers in the Shortcuts app.

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 Derive

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

The app will indeed be relaunched using Region Monitoring even if force quit. Reliability problems usually occur if the region around the station is not suitably set. There are a number of reasons, and some misplaced expectations on how region monitoring works that could be causing this: the region could not be placed correctly. A common issue is to use coordinates from a map or obtained otherwise. As region monitoring is based on WiFi and mobile signals, and those are affected by attenuation and reflections, as far as region monitoring goes, exact coordinates from a map may not be in the correct position. So, if you are having an issue with a certain location, you may want to double check that you see yourself located at the correct place and get the center coordinates according to live location rather than using a map or otherwise obtained coordinates. the region could be too small. Depending on the environment, the minimum radius could vary between 100 to 500 meters (and sometimes more, in rural areas). If