As far as I understand it, "Groups" in Xcode are simply a way to organize your project's files. However, I have found that classes in groups can't access the classes that aren't in the same group or children of that group. This makes no sense to me. Example: Group A -ClassA Group B -ClassB I want to declare: class ClassA: ClassB but I get the error "Cannot find type 'ClassB' in scope" However, if I move ClassB into Group A, it works. Is this a bug?

I'm new to SwiftUI, and struggling to figure out what seems like should be a very easy thing to do. Let's say I have a HStack with two images. I want one image to always be anchored to the top left of the area and one images to always be anchored to the top center. I think most peoples' first thought is "easy, just add a Spacer() after the second image." That doesn't keep the center image centered. I have resorted to making two VStacks inside a ZStack, and each VStack has one image with a Spacer() below it to make the images align at the top like I want, and the VStack for the top-left image has an HStack inside so I can add a Spacer() to force it to align left. This seems extremely hacky just to have two images with two basically anchoring points, and isn't very flexible as far as putting it into a new swift view class to modularize it since the whole thing relies on the full height of the screen.

I'm new to Apple watch mainly because I am trying to develop a companion app. New as a user and a developer for Apple Watch. I'm following an official Apple tutorial, but it seems to make a lot of assumptions. App groups Complications (horrible choice of terminology?) In the "Update Current Complications from iOS apps" step, I have no idea how to do what it's saying. https://developer.apple.com/documentation/watchconnectivity/using_watch_connectivity_to_communicate_between_your_apple_watch_app_and_iphone_app How do I choose a "Modular" watch face? What constitutes a "Modular" watch face? I deep pressed the current (default) face and it went into an edit mode, but swiping right didn't do anything. Swiping left offered more options, but I don't think it aligns with what it's saying to do. Stuck at 1 & 2 Stuck at 1 & 2

The instructions for submitting IAP say that you have to submit it with a new build. Is it possible for that build to be a TestFlight build? It doesn't make sense to me that an app would have to go live, then submit an update for that just to get IAP reviewed. Maybe I'm misunderstanding something, although Apple's doc's have been known to be inaccurate and/or misleading. In other words, if I want to test IAP in TestFlight builds before the game is ever released live, will it work if I submit a build for review and use the manual release option, but never release that version?

I have successfully signed, notarized, and stapled. However, I'm trying to script as much as possible to make it easier to automate. I am very confused about the staple step, since it doesn't have an argument for what is being stapled to the target app. This makes me unsure whether I can make this call from a different working directory (in bash) and still have it know what to staple.