Anyone run into this situation? I am using a TabView for iOS App and also decided to use a ToolbarTitleMenu on a couple of the Main views. Everything works as expected on iPhone versions of the App because the tabs are displayed along the bottom. However on iPad they are "floating" in the top middle of the screen and therefore completely obscure the ToolBarTitleMenu selector. Is there a way to get around this? I am surprised that Apple would have a standard control that does not work well on these two devices. Of course I can do a compiler #IF but would like to know if there is something I am missing here.

I have been trying to use TipKit popovers in my App. They all behave as expected in the simulator but on a real device I am seeing some strange behaviors. I have a couple of instances of where the tip is displaying an entire sheet instead of just the popover. In another case I cannot dismiss the Tip. Has anyone seen these behaviors and are there known issues/workarounds for this? I am reluctant to use something that works perfectly in the simulator but gives unpredictable results on a device. Not a good user experience in my opinion.

I built a SwiftData App that relies on CloudKit to synchronize data across devices. That means all model relationships must be expressed as Optional. That’s fine, but there is a limitation in using Optional’s in SwiftData SortDescriptors (Crashes App) That means I can’t apply a SortDescriptor to ModelA using some property value in ModelB (even if ModelB must exist) I tried using a computed property in ModelA that referred to the property in ModelB, BUT THIS DOESN”T WORK EITHER! Am I stuck storing redundant data In ModelA just to sort ModelA as I would like???

I have been developing an app for some time and tried distributing it via TestFlight to a couple of close friends but was getting crashes. It was an odd SwiftData Predicate thing that only showed up on TestFlight builds and not on builds downloaded from Xcode. Bottom line is I have created a whole bunch of unwanted version numbers thinking (incorrectly) that I needed to advance both the version number and the build number when uploading. The App has never been released so actually not even version 1.0 and I had created a bunch of versions all the way up to 1.11 before I realized my error. Now I am using a version 0.9 and just increasing the build number as I iterate thru external beta versions. The problem I have now is that TestFlight is still offering the version 1.11 build as the latest version to testers and I need to tell them how to ignore that go to the App in TestFlight and navigate to the "Previous Builds" under version 0.9 and download the latest build from there (this is tedious and confusing to those unfamiliar with TestFlight which is almost everyone who is not a developer). THE QUESTION IS: CAN YOU CLEAR THE VERSION HISTORY IN THE APP STORE FOR AN UNRELEASED APP? IF NOT HOW CAN I FIIX MY ERROR SO THAT MY FIRST RELEASED VERSION OF THIS APP IS FOR VERSION 1.0?

I have been building a SwiftUI/SwiftData app for some time that has been working fine in both the simulator and devices I have loaded from Xcode. These include two iPhones an iPad and a VisionPro. I have gotten to the point where I wanted to do some external beta testing so uploaded the App to the AppStore and then had a couple of users download via TestFlight. Unfortunately the App crashes and I have been unable to figure out why based on the feedback that I have gotten. The app has 4 Models that are linked in a fairly straightforward manner. There is a Habit class that is the central object. An Aspiration class that may have several Habits associated with it. An Anchor Class and a Celebration Class both attach to a Habit. I was able to get my neighbor to use TestFlight to download the App and it crashed when trying to insert a Habit but Aspirations, Anchors and Celebrations work fine and can be added, stored and deleted without issue. I then had my neighbor connect their phone to my computer and I download the app directly and it works fine as expected even when not connected to the debugger so clearly something is different between the two environments and I am at a loss so could use someone with good knowledge to help me figure this out.