Did you try clearing the contents of the Derived Data folder? Product > Clean Build Folder Or the more drastic version Quit Xcode Delete the contents of the "Derived Data" folder Run the app again

Your code does not compile, as you have not defined "Number" The actual error is "Cannot find 'Number' in scope".

Your code works as expected, when I run it (as your screenshot 2). Preview shows the first List (as your screenshot 1). I would suggest changing the "HSplitView" to an "HStack", as that seems to make both the app and the Preview work.

In a new Project, running on Xcode Simulator: iPad mini (6th generation) UIScreen.main.bounds.size: 744 x 1133 This is what I would expect Turn on "Requires full screen" Still 744 x 1133 (which is what I would expect I don't see where your 768 x 1024 is coming from! Xcode 13.2.1 (13C100)

If you are seeing 1024x768 points, for an iPad Mini 6, then you have a problem somewhere. As @Claude31 says, this is not the size of an iPad Mini 6, which is 2266-by-1488 pixels, or 1133 x 744 points. You may need to double-check why you are reading the incorrect dimensions. (I have a Mini 6, if a "real" device could help in some way.)

What you are calling "classes" are actually "structs" (so you may need to read up on the basics of Swift and SwiftUI). You have two Views, but no Model or ViewModel. There does not seem to be any need to have Text( Add_new_presets.username) in your ContentView, so the simplest quick fix would be to move that into the Add_new_presets View.

Try this: let columns: [GridItem] = [GridItem(.flexible()), GridItem(.flexible()), GridItem(.flexible())] struct ContentView: View { var body: some View { GeometryReader { geometry in VStack{ Spacer() ZStack { LazyVGrid(columns: columns) { Group { Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) } Group { Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Circle() .frame(width: 100, height: 100) .foregroundColor(Color(.systemBlue)) .opacity(0.5) Rectangle() .frame(width: 200, height: 80) .foregroundColor(Color(.systemBlue)) .opacity(0.5) .cornerRadius(60) .position(x: 114, y: 55) Circle() } } } Spacer() } } } }

You've got more that 10 Views in your LazyVGrid. Try dividing them into two Group views (5 in one, and 6 in the other).

Yes, the user must respond to the first notification, to action the second. I don't see any way round that.

Interesting that no-one has chimed in to say how much they like to have twice-a-week updates!

Some options; Un-cancel the previous developer, and get them to transfer the app to the new account (best solution) Submit the app with a new name, on a new account, and hope that Apple don't notice that it's a copy of an existing app (dodgy solution) Create an all-new app, and submit it using a new account (acceptable solution) Negotiate with Apple, to transfer the existing app without involving the original developer (unlikely solution)

It's an interesting idea. I guess it is technically possible, but I wonder if it will work in practice? I would suggest you start with a feasibility study... If you start at the DAW end, and do all the Midi and comms work, and then it doesn't work out when the band is playing (e.g. maybe the "beat" isn't distinctive enough to follow), then you've sunk a lot of time into it. I would start with a simple Apple Watch app that gives a steady beat (at the rhythm of some song, or maybe adjustable), and see if it's something that a musician could follow, while the band is playing. On a related sidenote, I thought Apple Watch haptics might help with navigation on the motorbike, but in practice I rarely notice the buzzes. I'll be interested to hear about possible technical solutions, if other people chime in. I suggest you add a list of the main issues that would need to be solved, (break it down a bit, as the original question is a bit too big). Good luck!

No need to shout!

One option is to use screenshots from Xcode's Simulator, to get different devices. File > Save Screen

I was having this problem, and it now seems to have fixed itself. Xcode is now showing the Simulators, as expected. See the original thread: https://developer.apple.com/forums/thread/696830?answerId=699203022#699203022 Xcode 13.2.1 (13C100)