Welcome to the forum. Do you call for some help ? If so, please provide useful information. Your present post is nearly useless. what do you mean by 'broader mathematical term' ? please, show the formula explain where you evaluate: in an app ? in playground ? in calculator app (likely, seeing your other post) ? elsewhere ? in addition, provide a screenshot.

You should file a bug report.

I have not found a really good solution to this. For the time being, I just ignore the warning. You may try to create your own modifier, where you would have the test for version. https://www.hackingwithswift.com/books/ios-swiftui/custom-modifiers   Additionally, in a newer project, I don't have to include the if #available(iOS 17.0, *) { }, so I'm guessing the build is made for a newer iOS. If that's the case, would it not be compatible with older iOS versions? It is not a question of new project. It is related to the minimum target you define. Or you can set minimum target to iOS 17 (but not so good).

In SwiftUI, you can hide the button with: .navigationBarBackButtonHidden(true) https://sarunw.com/posts/hide-navigation-back-button-in-swiftui/#:~:text=To%20hide%20a%20navigation%20back%20button%20in%20SwiftUI%2C%20we%20apply,(true)%20to%20the%20DetailView%20.

Did you see this, suggesting to temporarily disable optimized battery charging on iPhone.: https://forums.developer.apple.com/forums/thread/756731 Hope that can help.

Do you mean that the app is NOT intended to be used by a specific business or organization, including partners, clients, or employees ? If so, you should explain it with convincing arguments in the comments to reviewer. But first, try to imagine why reviewer came to that conclusion, that will help write a more convincing explanation. Good luck.

Predictive code completion requires a Mac with Apple silicon, running macOS 15. Did you install MacOS 15 ? AFAIK, the model is 2.5 GB. so over a 5 mbps (bits, not Bytes), that require at least 1 hour at full speed, so practically probably 2 or 3 hours, if it can complete. But yes, a progress bar should be a good thing.

There is no attached image… Removal is done via Pricing and availability page. Is it where you go ? REad here: https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/manage-availability-for-your-app-on-the-app-store Remove your app from the App Store in all countries or regions From Apps, select your app. The page opens with the Distribution tab selected. In the sidebar, click Pricing and Availability. Scroll to the bottom of the page, and click Remove App From Sale.

SwiftUI lists are lazy loaded: so they load when you scroll. See discussion here: https://forums.developer.apple.com/forums/thread/651256 And yes, cells are reused. Could you show the code ? If data contains thumbnail and HD, it is normal that both are loaded. What did you expect ? What do you want ? Could you create another State var, with only thumbnail, and show HD only when tapping the thumbnail ? It all depends on your spec.

Another interesting reference: https://www.appsdeveloperblog.com/create-uicollectionview-programmatically-in-swift/

Are you looking for the location where the photo was shot ? It is location property in PHAsset: https://developer.apple.com/documentation/photokit/phasset Some sample code to access here: ttps://mobikul.com/phasset-in-swift/ Hope that helps.

Have you searched for tutorials ? Some here: https://medium.com/@thenoobdev10/programmatic-uicollectionviewcontroller-tutorial-925f009c98a7 They explain how to create a property for layout and initialize collectionViewController with flowLayout. Update in AppDelegate

You should file a bug report. When you search, you can select the order: Most relevant, last updated… Doesn't it help ?

Have you checked the dates of the certificates ? Is one of the duplicates greyed out ? IMHO, it should be no problem (unless you have another underlying problem in the system configuration). Only the valid one is used.

What are the differences between @State, @Binding They both refer to state var in the View. But @State var "belongs" to the view @Binding var "belongs" to another view, that means there is another State var in the other view that share the same pointer. So when you change var in the other view, it is also changed in the first. There are many tutorials to explain, like these ones: https://www.hackingwithswift.com/quick-start/swiftui/what-is-the-binding-property-wrapper https://www.hackingwithswift.com/quick-start/swiftdata/whats-the-difference-between-bindable-and-binding