Yes, that's a clean way to do it with func collectionView(_ collectionView: UICollectionView, targetIndexPathForMoveFromItemAt originalIndexPath: IndexPath, toProposedIndexPath proposedIndexPath: IndexPath) - IndexPath And gives equivalent result to what I proposed. Note: for user experience, alerting (as I explained) why he cannot move would be useful.

self.sceneView.center.x = 195.0 self.sceneView.center.y = 422.0 Are they the expected values ? What type of outlier do you think of ? Did you try to debug the view hierarchy ?

That's just a personal opinion. I sleep it down and reboot from time to time (less than once a week).

I would change code with:                 ForEach(networkController.users, id: \.self){ user in and use user.weather later in the closure (you did not show what you do there, so hard to say more).

When I breakpoint in this extension: extension UITextField { func validateTextField() { print("validateTextField", self.text!) } } It does break. I use Xcode 12.4.

So, you have a code that was developed with Xcode 6.4 ? Which Xcode do you want to use now ? You may have to upgrade several times, correct the code each time, with intermediate versions of Xcode (something like): 6.4 - 8 8 - 10 10 - 12 You can download older versions of Xcode here : https://developer.apple.com/download/more/ Another way is to create a new project, rebuild the Storyboard and paste as much code as you can. Så har du en kod som har utvecklats med Xcode 6.4? Vilken Xcode vill du använda nu? Du kan behöva uppgradera flera gånger, korrigera koden varje gång, med mellanversioner av Xcode (ungefär som): 6.4 - 8 8 - 10 10 - 12 Du kan ladda ner äldre versioner av Xcode här: https://developer.apple.com/download/more/ Ett annat sätt är att skapa ett nytt projekt, bygga om Storyboard och klistra in så mycket kod som möjligt.

May have a look here for some preliminary answer: https://stackoverflow.com/questions/55077716/ios-watchos5-how-to-detect-programmatically-if-apple-watch-was-on-the-wrist-w May be you could also look at heart rate history and if nothing changed in the last 3 or 4 frames, that could mean the watch is no more on wrist, and thus ignore the measures ?

You didn't declare your class Equatable. You should try to add this protocol. class Month: Hashable, Equatable Otherwise, AFAIU, you use the standard == to compare instances, hence the references.

I don't understand what you want to show in Section and what you do in ForEach. In addition, your naming of var is awfully confusing main used in different places for different things users as plural but not an array… weather singular but several values in array If I understand what you want to do, you should probably: Section { ForEach(networkController.users.weather ?? [], id: \.self){ userWeather in // rename user Text(userWeather.main ?? "") } // ForEach is meaningless here ForEach(networkController.users.main ?? Main(temp: 0), id: \.self){ user in // Text("\(user.temp)") Text( "\(networkController.users.main ?? Main(temp: 0)).temp)") }

That's the problem with such complex definitions in your code… There is probably a missing parenthesis before .temp (to be balanced by another leading one. Text( "\(( networkController.users.main ?? Main(temp: 0)).temp)")

I do not know of any authorisation key for this in info.plist. And no Privacy key. For me, that means it is not required to ask user. One advice: when you submit the app, explain you change the icon in the comments to reviewer. That will avoid any further problem.

I found old SO threads, but you should adapt to better understand where the problem is: https://stackoverflow.com/questions/22443425/application-loader-stuck-at-authenticating-with-the-itunes-store-when-uploadin and https://stackoverflow.com/questions/50507628/unable-to-upload-the-ipa-file-to-itunes-store You should check your account (here is the sequence): I checked my Appstore Connect account (contracts). I noticed a yellow warning that some contact information were missing. I updated.

Which version of Xcode ? That was supposed to be solved in 11.2: "Fixed an issue with UITabBarController where decoding an instance from a storyboard would create extra views at the left end of the screen. If you worked around this issue on Xcode 11.0 or 11.1 by creating a subclass of UITabBarController and hiding extra views in the initializer you can remove the workaround. (55310448)"

I noticed similar problems with List. First try to replace by VStack, just to check. If that works, that is a List problem. If not, maybe problem with images. Did you put them in xcassets ?

I would try to replace here: return List { ForEach(menus) { menu in self.destinationView(menu: menu) }}} with return Stack { ForEach(menus) { menu in self.destinationView(menu: menu) }}} If that works, you should file a bug… and close the thread.