This has stopped working in iOS 15. I'm looking for another workaround. The widths still split 50/50 as desired, but the touch target area seems to overlap, so dragging on the first picker causes the second wheel to scroll, unless you touch way towards the edge of the screen.

Are you getting wheels or menus? I had to add .pickerStyle(.wheel) because the default seems to have changed. I forgot to add that to my question. I will edit the question now.

I just pasted your exact code into a new project, and it causes the problem for me. The border between the touch areas is way right of center, not in the center as it should be. I'll add an 'answer' with a screenshot, in a moment. I thought I could edit my question to add a screenshot, but apparently I can't.

Yup, that fixes it. Thanks.

Found an answer: add .compositingGroup() modifier to second picker to fix the touch target issue.

In the package, do you have a .h file containing types for the metal shaders? Or did you just paste the types into the .metal shader files? I tried the former, but I don't think the .h file was being picked up my the .metal or the .swift files. Maybe I need to say something in the Package.swift to tell it about the .h file.

I just tried a \< (backslash escape), and that still triggers the monospace for me.

You didn't get the 3 bar icons on the right side, after tapping "Edit". That's odd. I see it on my device. You drag that to move them. As for the circles, I left that to you. Now it just turns the text green, but you can conditionally draw a colored circle using SwiftUI shapes, like Circle.

I just got this working. Thank you! Besides waitUntilCompleted as you recommended, I also switched from MTKView to a lower level technique using CAMetalLayer (following an Apple sample project named "CustomMetalView"). That may not be necessary but in my situation it helped. Now when I'm in LLDB and I step across a change in the data model, I can call a certain Swift function (p debugRender()) and I see the change on my device screen. Sweet!

Same here, also with a 4000 line Swift file. Now I need to redesign my application code around Xcode's problems.

For some of my dead links, I have enough notes about what was in them to find them again using search engines. But for others, no. For this one the note is basically: "remember this about keychain: link". If they were going to break old links, they should have added a way to find by old ID. Eg, a search query like old_id:281700.

Okay, "Files and Folders" might work. The first file that gave the error had a path like "~/Workspace/MyProject/main.jl". That "Workspace" directory is where I have a lot of software dev and other projects. And yes, it's a GUI app that the user would normally click on in Finder. I think I want permissions similar to Xcode. The app is going to be editing different kinds of files: scripts, programming language code files, and custom "project" files that are SQLite databases. It's an app for creating 2D and 3G generative art. So it will probably open "Projects" that are directories full of files, but I would also like it to be able to edit random files. (So, similar to how Xcode works in that respect.)

Oops, forgot your last question. The Signing Certificate popup says "Development" now. I'm sorry, I don't know what you mean by "stable code signing identity". For some of my other projects, which are iOS apps deployed in the App Store, that item is not a popup and it does not say "Development". It will say something like "Apple Development: [My Name] ([alpha-numeric code])". This macOS app that I'm asking about has no App Store record (maybe someday).

Yes, it's sandboxed. Should I just turn that off? It was the default when Xcode created the project. It seems like the ideal is to leave it on and enable access to resources as needed. ?

Okay, thanks! I'll need time to try out these suggestions and post back later if I'm stuck. I wonder how recursive are the security-scoped bookmarks? Could I simply ask for access to /Users/joe or /Users/joe/Workspace and have read/write access to everything under it? I'll find out when I experiment some today.