file uri scheme

Thanks again @RickMaddy I nicely added items to the File Menu using your example. As it turns out I was way overthinking this. I thought there would be a unified menubar in multitasking, not a per window one. This is much simpler and answered my, where is it in Vision, question. I don't really know how I missed this point in the intro video. The only other note I will point out for any other dinosaurs following along is that this line [super buildMenuWithBuilder:builder]; only works with supers that are UIResponder subclasses. So if you started your project in iOS 4.x your AppDelegate might still be an NSObject subclass, and you should upgrade to eliminate some build warnings.

Hi, thanks for mentioning the .exp file approach. This works well with the scenario I explained above (dynamic framework depending on static libs). However, when I tried this with a slightly different project configuration, I faced linker errors. I replaced the static libs with dynamic libs. So, now I have a dynamic framework with 3 target dependencies, each being a dynamic library. This project builds and runs fine when tested on the iOS simulator. But according to our other discussion here, when I test this on a real iPhone, it builds fine but fails at runtime with a linker error: 0_abort_with_payload and Xcode shows the following assembly instructions specifying the error Thread 1: signal SIGABRT - dyld`: 0x1aa0a15f8 <+0>: mov x16, #0x209 0x1aa0a15fc <+4>: svc #0x80 -> 0x1aa0a1600 <+8>: b.lo 0x1aa0a1620 ; <+40> 0x1aa0a1604 <+12>: pacibsp 0x1aa0a1608 <+16>: stp x29, x30, [sp, #-0x10]! 0x1aa0a160c <+20>: mov x29, sp 0x1aa0a1610 <+24>: bl 0x1aa040064

I confirm that the issue is still there in Xcode 26.1 Beta 2. When the Default Actor Isolation (SWIFT_DEFAULT_ACTOR_ISOLATION) is set to MainActor, the compiler adds @MainActor to the subclass of NSManagedObject, which makes the attributes added to the subclass MainActor-isolated, and triggers the warning. Unless you'd change SWIFT_DEFAULT_ACTOR_ISOLATION back to nonisolated or live with the warning, the Swift forum post you provided mentions the following options: Create a nonisolated variable to hold the closure, and call the closure from within the perform method of the managed object context. Manually create the entity class (the subclass of NSManagedObject), and annotate it with nonisolated. These options work, but are not ideal. The best solution may be that Xcode annotates the entity class with nonisolated when generating the code, but that needs to be implemented in Xcode. I'd hence suggest that you file a feedback report – If you do so, please share your report ID here. Best, —— Ziqiao Chen

I apologize for the inconvenience you have experienced. I have attempted to replicate the issue in Xcode 26.1 and have verified that the language is correctly set. Could you please provide me with the version of macOS and Xcode that you are currently using? If the issue persists, I recommend attempting the latest versions of each. Additionally, if you are unable to resolve the issue, I would appreciate it if you could file a bug report. 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.

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

Hi, I am trying to load files from the Apple Vision Pro's storage into a Unity App (using Apple visionOS XR Plugin and not PolySpatial package). So, my immediate question here is what your larger goal here actually is? visionOS generally uses the same file access model as iOS, which means apps get access to files through one of two broad mechanisms: The files are added to one of the app’s container directories. There are many different APIs that use the broad flow, but the simplest case is having your app appear in File.app so that the user can directly add files. Basic access can be enabled by setting UIFileSharingEnabled and (possibly) LSSupportsOpeningDocumentsInPlace. The app uses an API like UIDocumentPickerViewController to allow the user to give their app access to specific files or directories. Finally, apps that are built around documents generally use the approach described in Building a document browser-based app, which actually provides a unifi

Adding FBs as I find them. FB20652137 Replace button wraps unfortunately. Going through all the built in functions menu by menu (Adding print was easy enough.) Added Find and Replace to my text views in storyboard, which automagically enabled the menu item and produced this view. I don't even have Text size that big in my iPad Air 13-inch sim. Also, in trying to see if you could replicate it with built in apps I notice that the input view I get is unlike the snazzy Pages built in keyboard. I wonder if there is a way I can adopt the Pages UX? I mean, I don’t mind the glass buttons but would like to choose the color for done (blue just doesn’t go with our look and feel). Or let me change the blue which really doesn't go with our Color scheme.

Have either of you filed a bug on this? If so, what's the bug number? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

While developing our driver, we've noticed that the *.ips report that contains the stack trace of the crash is not always generated. To be clear, you're talking about DEXT level users space crashes, NOT kernel panics? I've assumed below that you're dealing with standard crashes, but please let me know if I've misunderstood. I'm wondering why this report may not get generated. So, the first step here is to figure out what actually happened, which means digging through the console log. In general, there are multiple components tracking (notably, launchd) any system component (including DEXTs) and they'll be notified of your process's death, including how/why it died. If you're on development hardware then there are some tips in Your Friend the System Log that can be useful for quickly getting at this sort of data; however, I'd generally trigger a sysdiagnose and use that console archive. The big advantage of the sysdiagnose is that you capture everything, which means you're not going to miss data if something u

Well, welcome. Most Apple documentation is a reference of API calls, generated from header files. It tells you how to spell them, what the parameters are, sometimes what those parameters mean, what OS versions you can use them in, and not much else. Learning from these resources is like trying to learn a natural language from a dictionary. Apple has some videos from WWDC presentations about new technologies, but these tend to assume familiarity with the language and the problem domain. In the olden days (maybe twenty years ago), I might have said get a book, but books are out of date the moment they are written. If you have access to an AI, I can recommend this approach. Prompt it with a program you have written in Python. Tell it that you are a Python programmer, and you are new to Swift, and that it should translate the program to Swift, and explain what it does and how the code compares to the Python implementation. Ask it to provide links to relevant documentation. Then read the explanation it pr

Ok, I think I got it to work. I think I was using the wrong build scheme. It appears to work when selecting the test scheme in xcode before running the tests. I think previously xcode would automatically switch schemes, or at least a prompt would appear asking if I wanted to switch schemes, I could be wrong, though. Thanks.

There are no known issues around this in Xcode 26. If you are using XCTest UI Automation style tests, please ensure you are accessing environment variables set in a test plan from your test runner process and not from the process of an app-under-test. If you believe this is a regression, please file a Feedback with Apple and include the .xcresult bundle from Xcode's Report navigator if possible.