I am currently testing an app under development and I recently added a HeathKit authorization request to allow the app to save some data in the Health App. Everything works fine when I compile the app in Xcode and run the app on my personal device but my TestFlight users are not seeing the request form appear and neither do I see it when I load the TestFlight version of the app on the same device I had used for running the app during active development (of course I had manually removed the previous version of the app and checked to see that the app was no longer appearing under the privacy section of the health app). Is there some type of restriction in place during TestFlight testing? I had not seen any such notice and was expecting all my testers would have had the ability to test this feature out on a variety of device types. Thanks for anyone who can shed light on this issue.

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 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 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???

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.