For the success of this project, it is essential to have precise information about the hardware components of specific iPhone models In that case your project is doomed. Give up and find a different project before it is too late. Your only hope is to measure these parameters yourself. Apple do not publish this sort of information.

I also find that the sandbox IAP server is very slow, but I've never had complaints from users so I presume that the production servers are much faster.

What country are you in? You don’t need to be VAT-registered if your turnover is below the registration threshold, but it can be beneficial to register voluntarily. Your receipts from Apple are an international business-to-business transaction, so are “reverse charged” i.e. in effect no VAT, but your expenses will likely be domestic (e.g. buying computers), so you reclaim VAT on them.

P.S. Have a look at the LLVM coding conventions, described here: https://llvm.org/docs/CodingStandards.html They say that they actually prefer using continue rather than extra indentation. This also reminds me that some people say that having multiple return statements in a function is bad.

The reason for disliking them is that they permit "less structured" control flow. GOTO permits totally-unstructured control flow. break and continue are like a restricted form of GOTO. Structured control flow is preferred because it is easier to correctly understand it when you read it. Remember, the next person who will read the code that you write will be a violent psychopath who knows where you live. Consider reading Djikstra's "GOTO considered harmful" paper. I don't know if you'll really understand it, but try. In my opinion, when you consider writing break or continue your should ask yourself "How could I write this otherwise, and would that be more or less clear?". If the alternative would be less clear (to the axe-wielding psychopath), then break and continue are fine.

NSFileCoordinator doesn't seem appropriate for SQLite at all. Use NSFileCoordinator when the file can't cope with simultaneous accesses. But SQLite can cope with simultaneous accessed. So no need for NSFileCoordinator.

I've no idea what Apple do. There are various corporate style guides that are available online, including Google's. The important thing is to understand why these things might be discouraged. If you're smart, you should imagine future-you writing a style guide for your subordinates, not blindly following one written by someone else. (If you're not smart, stop asking questions and just do what you're told!)

It requires SF Symbols 5, which is in iOS 17.

It doesn't matter, the results are better from a proper search engine.....

we observed disparities between the figures displayed in the dashboard and those obtained through the APIs. Which dashboard figures, and which API figures, precisely, are you comparing?

Apple would like you to buy search ads.

I guess you have set 32 bits per pixel, right? Does your data actually have 32 bits per pixel, or 24?

in testing and I only get "1.0" as originalAppVersion within the beta release Development versions always report 1.0. In production it does report whatever is in CFBundleVersion. For my apps, in the past that was set manually to 1.2.345667. Now I think it automatically gets set to just the 34567 part. All you really need to know is whether the version is “new” or not. So if your first free version is 2.0 build 1234567, then check for anything that contains “2.0” or “1234567”, and consider everything else “old”.

Try 17 . * . * . * I don't know for sure if this Apple range is always used by App Review, but I don't think they will give you a list of IPs so it's worth trying.

The App Store has a feature that allows users to download the most recent supported version. So I think in answer to your question (1) they can re-download the old version of the app when necessary, (2) they can't purchase it.