I couldn't find any information on this, this is what I what I think. UILabels don't have a NSLayoutManager where the default value for .usesFontLeading is true, if that's true, then this is how it goes: boundingRect doesn't require the usesFontLeading option in my cause because I'm only using UILabel and not UITextView, bigger code repositories use .usesFontLeading because they either solely rely on UITextView or want to make their apps more inclusive of elements. That's what I think, I won't mark this post as the answer because there is no proof backing up my hypothesis. If any one of you know why that is the case, then feel free to post your answer. Hopefully this helps someone. Cheers.

Hey, can you please share what API you're using and the basic concept of your app? Some screenshots would be helpful too.

Can you please post the basic concept of the app with some screenshots. When publishing an app on the App Store, the first thing you should focus on the amount of features and the overall goal of the app. I suspect you're releasing your merchandise store as an app?

Almost 8 months later, and here are my thoughts on the issue, 8 months ago, SwiftUI was pretty new and had a lot of hidden bugs, especially in testing. The problem I think I had was that when testing in debug mode, the system would perform more calculations and since I was rendering a lot of images in LazyVStack, which is good for lazy-loading but throttles when you feed in too much stuff, after scrolling through 25 images, the LazyVStack started throttling which caused the app to freeze. This is my own thinking, Apple never responded back, even though I used one of my incidents, and even sent all the copyrighted code. My solution to this problem was: Just migrate to UIKit, SwiftUI is too young for complex applications with a lot of images and network requests, it just can't handle all the pressure. Hopefully this helps someone.

Building an app is like building a web app, you share data with the server and store all of it on a database which is on the same server as your API. Unless you wanna use a server less solution, my best bet for a server less solution would be Firebase, if you are down for an API based approach, then build an API using Express, Django, whatever, and use MySQL, PostgreSQL, Cassandra for your database. To get started with APIs, you can go here: https://www.youtube.com/watch?v=-MTSQjw5DrM Not my channel, Fireship also has tutorials for mobile apps, firebase, etc.

Try cleaning your build folder, by pressing: Shift + Command + K