Sure would be handy if Apple included some information about the requirement to open Xcode to complete the agreement process.

I'm seeing the same issue, with a Unity-generated project. I don't think moving headers around in the project is a solution for Unity-generated projects, since the whole project gets regenerated every time I build. I can just do a "Clean Build Folder" and then it builds again without having to regenerate the whole project. I hope Apple fixes this issue, but I have low hopes that they're paying attention.

I have figured this out. What's not obvious is that this project has a Watch Extension target. I am sharing many of the classes between the main iPhone target and the watch target, which requires checking the box for the watch target when the class is under the phone project structure. I had forgotten to check the box for the watch to have access to the new class BleMessenger.swift. It would be extremely helpful if the error message was more specific, but I guess it's just something to remember.

When I put the class file "BleMessenger.swift" into the "Data" group, the classes in the "Gadgets" group can't see it. If I move the "BleMessenger.swift" file into the Gadgets group, suddenly the classes in the "Gadgets" group see it. As shown, the BleMessenger class is currently empty. Here are screenshots of the issue:

Ok, my example wasn't exactly my use case. I'll revise... Group A -ClassA -Group B (is inside of Group A) --ClassB ClassB cannot see ClassA. (edit: This works in a new project, so I guess I'll have to get screenshots from my actual project.)

I think I found the answer I wanted in "overlay", which allows anchoring additional items within the space of another item, at corners or centered along edges. // // MainView.swift // DB5 Remote // // Created by Todd Gillissie on 1/10/22. // import SwiftUI struct MainView: View { @State private var playingVideoId = "" @State private var mode = AppMode.MODIFICATIONS   var body: some View { ZStack { GeometryReader { geometry in Image("BackingTexture100") .resizable() .aspectRatio(contentMode: .fill) .scaledToFill() .ignoresSafeArea() } // Top left & right // VStack // { // HStack { // Image("007LogoWhite") // .resizable() // .scaledToFit() // .frame(width: 120, height: 40, alignment: .topLeading) // Spacer() // // PancakeMenu() // } // Spacer() // } // .padding(.horizontal, 8) // Horizontally centered from top to bottom of screen. VStack { Image("MI6logo") .padding(.bottom, 6.0) DB5LogoTitle(mode: mode) // switch statements don't work in views for some reason.. if (mode == AppMode.MODIFICATIONS) { ModificationsView() } else if (mode == AppMode.VIDEOS) { VideoList() } else if (mode == AppMode.CREDITS) { Rectangle().foregroundColor(.yellow) } } .overlay(alignment: .topLeading) { Image("007LogoWhite").resizable() .scaledToFit() .frame(width: 120, height: 40, alignment: .topLeading) } .overlay(alignment: .topTrailing) { PancakeMenu() } .padding(.horizontal, 8) if (playingVideoId != "") { VStack { Spacer() PlayingVideo() } .padding(.horizontal, -4.0) .ignoresSafeArea() } }   } } enum AppMode: Int { case MODIFICATIONS = 0 case VIDEOS = 1 case CREDITS = 2 } struct MainView_Previews: PreviewProvider {   static var previews: some View {     MainView()   } }

This is how I'm currently doing it. There's a separate VStack just for the top right and top left elements ("007LogoWhite" and PancakeMenu) struct ContentView: View {   var body: some View { ZStack { GeometryReader { geometry in Image("BackingTexture100") .resizable() .aspectRatio(contentMode: .fill) .scaledToFill() .ignoresSafeArea() } // Top left & right VStack { HStack { Image("007LogoWhite") .resizable() .scaledToFit() .frame(width: 120, height: 40, alignment: .topLeading) Spacer() PancakeMenu() } Spacer() } .padding(.horizontal, 8) // Horizontally centered from top to bottom of screen. VStack { Image("MI6logo") DB5LogoTitle() .padding(.top) Spacer() } .padding(.horizontal, 8) }   } } Here's what it loooks like so far... obviously it will have more things in the second VStack for more content under the DB5LogoTitle() element.

Thanks for the link, I'll check it out. I still think that naming anything "complications" in software development is a horrible idea. This isn't clockmaking. That's like naming a feature a "bug" because that was the traditional word in some ancient profession.

Same.