xcode github

I've reproduced this on these 2 setups using the same iCloud account: Xcode 26.0 beta 4 (17A5285i) & iPhone 12 running iOS 26.0 (23A5326a) Xcode 16.4 (16F6) & iPhone 16 Pro running iOS 18.6.1 (22G90) Deleting the iCloud data for the app from one device also allows me to reproduce the issue on the other device. The error printed in the sample project by the console is: You don’t have permission to save the file “Documents” in the folder “iCloud~com~hfriia~SimpleiCloudDocument1”. Failed to save a document! I just tested on this setup using another iCloud account and it functions as expected - I can immediately recreate the documents folder and save a document: Xcode 26.0 beta 4 (17A5285i) & iPhone 7 running iOS 15.8.4 (19H390) Xcode 26.0 beta 4 (17A5285i) & iPhone XR running iOS 18.6.1 (22G90) Maybe there's something wrong with the first iCloud account?

Seeing same issue with Xcode beta 6 on iOS 18.

So, let me start by going back to here: (1) If I try to add this to CallDirectory.entitlements manually com.apple.developer.callkit.call-directory That entitlement does not exist and never has. (2) call-blocking caller-identification More broadly, the vast majority of our entitlements use simple boolean values, not arrays or other complex data structures. The two exceptions I'm aware of are DriverKit and the Network Extensions, both of which require specialized support on the portal. If we did have this entitlement (which we don't), it wouldn't work like this. On our paid Apple Developer Program account (role: Account Holder/Admin), the Call Directory capability toggle does not appear on any iOS App Extension Identifier we create. Yes. You're looking for something that does not exist. As Quinn said: My best guess is that these entitlements are being ‘hallucinated’ by an LLM. This isn't really a guess. We've been seeing more examples of this happening. Similarly: My specific advice is that you not add entries

This seems to be fixed with Xcode 26 beta 6. I am now able to run the iOS 17 and 18 simulators, as well as build to my device again.

[quote='854568022, ssnao, /thread/797299?answerId=854568022#854568022, /profile/ssnao'] I have already filed FB19729881 [/quote] Thanks. It’s helpful to include bug numbers in your forums posts so that (Apple folks at least) can see the extra context. iOS 26.0b7 (23A5326a) landed yesterday. Have you had a chance to try things out there? If not, please do, and then update your bug with your results. Now, I just happen to have a 26.0b6 (23A5318c) device that I haven’t upgraded to b7 yet, so I thought I’d give this a try. I created a new test project and added code like this: do { print(will run task) let url = URL(string: https://i.socdm.com/sdk/js/adg-script-loader-b-stg.js)! let request = URLRequest(url: url, cachePolicy: .reloadIgnoringLocalCacheData, timeoutInterval: 60.0) let (data, response) = try await URLSession.shared.data(for: request) let httpResponse = response as! HTTPURLResponse print(did run task, status: (httpResponse.statusCode), bytes: (data.count)) } catch let error as NSError { print(did not

This is NOT corrected in Xcode 26 beta 6 / iOS 26 beta 7

This is corrected on Xcode 26 beta 6 / iOS 26 beta 7, marking FB18995026 closed, thanks!

This is NOT corrected in Xcode 26 beta 6 / iOS 26 beta 7

Hi Ziqiao, thanks for the code snippet — it also works well in my app. I only made a few small changes: I’m using NavigationSplitView instead of NavigationStack, and placing the List inside the navigation view slightly changes the appearance of the navigation bar. It now returns directly from the detail view to the document browser. Also, the sheets and full-screen covers you present should now show the document title and back buttons in their navigation bars. Xcode 16.4 iOS 18.3 iPhone 18 Pro (Simulator) struct ContentView: View { private enum Row: Hashable { case details } @State private var selection: Row? var body: some View { TabView { Tab(Rectangle, systemImage: rectangle) { NavigationSplitView { List(selection: $selection) { NavigationLink(value: Row.details) { Text(Tap to see details) } } .toolbar { ToolbarItem(placement: .topBarTrailing) { Button(Add) { print(Button pressed.) } } } } detail: { switch selection { case .details: Text(Details) default: Text(Select something) } } } Tab(Circle, s

[quote='853475022, oikawa_yoji, /thread/796579?answerId=853475022#853475022, /profile/oikawa_yoji'] The same source code is included in the Xcode project attached to the email I sent [/quote] Got it. Thanks. I ran your project and was immediately able to reproduce the problem. Specifically: I’m using Xcode 16.4 targeting the iOS 18.5 simulator. I ran the app from Xcode and it exited as expected. I then ran the same app from the simulator’s Home screen and it crashed. Here’s the backtrace from the resulting crash report: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib … __pthread_kill + 8 1 libsystem_pthread.dylib … pthread_kill + 264 2 libsystem_c.dylib … abort + 100 3 libsystem_malloc.dylib … malloc_vreport + 896 4 libsystem_malloc.dylib … malloc_report + 60 5 libsystem_malloc.dylib … ___BUG_IN_CLIENT_OF_LIBMALLOC_POINTER_BEING_FREED_WAS_NOT_ALLOCATED + 28 6 cccccccccccc.debug.dylib … __debug_main_executable_dylib_entry_point + 268 (main.cpp:103) 7

Sadly, I don’t read Chinese, so I’m responding based on a machine translation of your post. Error -1009 is NSURLErrorNotConnectedToInternet. This can have a wide variety of causes, so it’s hard to track down exactly what’s going on here. However, it’s certainly weird that: You’re consistently seeing this failure on phone A but not phone B. Phone A works when you install your app with TestFlight. Your full error message contains a useful titbit: [quote='797264021, flj, /thread/797264, /profile/flj'] unsatisfied (Denied over Wi-Fi interface) [/quote] This is very solid evidence that your app’s connection is being blocked by NECP. For some general background on NECP, see A Peek Behind the NECP Curtain. Notably NECP is blocking your access to Wi-Fi. That’s unusual because on most phones NECP only limits access to WWAN. I’m presuming that your phone was bought in China, and thus has the ability to limit an app’s access to WWAN and Wi-Fi. When NECP goes wrong my usual recommendations are: Restart the device. Reset