The downgrade is no doubt a power-saving feature. Presumably Apple have some complex and secret algorithm about how and when it upgrades after you start using it again.

Apple don't tell us details of the "actual users". "Client" is I think always "App Store". It may differ for other content, e.g. music.

Uploaded builds are shared by both App Store and Testflight, i.e. after you have successfully testflighted a build you can send the exact same build to app review. I don't suggest trying to automate submitting builds to app review. You will want to manually review the app metadata etc. before pressing "submit" in the web interface.

We have a long thread about iTMSTransporter on Linux over here: https://developer.apple.com/forums/thread/719443 Your error message looks different though…. How recently was it working for you?

I believe "copy" means that it copies the object you supply when you assign to the property. It's not relevant when you read from the property, as in your url = self.sourceURL example.

Does this apply to ALL methods with the word "init" in the name, even if the function is "initialCapitalizationMode", in which initial does not mean the same as init? No. Or does it only work if it has "init" and then an uppercase letter after the fact? Yes. Well, I’m not sure if the uppercase capital is a sufficient test, maybe there are some other exceptions.

Do these other developers have Macs?

Why you give same question dude ?i have answer your question I asked if you have any warnings, and you replied that you didn’t have any errors. Errors and warnings are different. Based on AndyJJ’s note that that symbol is iOS 14 only, and as you’re compiling for iOS 12, you should get a warning from the compiler about that. So there are a couple of possibilities; one is that you are ignoring the warnings, in which case “naughty, don’t ignore the warnings!”, or for some reason the warning is not being generated, in which case that needs to be investigated, e.g. in your build settings. P.S. Don’t post comments in this forum, always post replies; comments don’t generate email notifications, which is why I’ve not replied for a week.

We have a long thread about this over here: https://developer.apple.com/forums/thread/719443 Your error seems different though - and do I understand correctly that it does work for you 30% of the time? That is good news if true! So maybe they have changed something on the server side. I see you are using -jwt, Have you also tried with username and password? I have started decompiling the java to look for the bug. This certainly looks like a tractable approach, i.e. the decompiled code is quite readable, but I don’t have much time to spend on it.

8GB will be fine.

The Apple Insider quote is odd. Obviously a totally-free app pays no commission, because it's totally free. Maybe he considers a "free with in-app-purchases", aka "freemium", app to not be a free app? I don't have a similar business model, but I am pretty confident of the following: whether an app is initially free or not does not influence whether Apple takes commission on subsequent in-app purchases. Here is a quote from schedule 2 of a developer agreement: 3.4 Apple shall be entitled to the following commissions in consideration for its services as Your agent and/or commissionaire under this Schedule 2: (a) For sales of Licensed Applications to End-Users, Apple shall be entitled to a commission equal to thirty percent (30%) of all prices payable by each End-User. That's followed by describing the reduced rate of 15% for subscriptions after the first year and the small business programme. No mention of a zero rate for IAPs for initially-free apps.

Because the app is available to download for free, Apple will not take a percentage of the "in-game-currency" revenue, correct or did I misread? No, that's not correct. Apple take commission on all in-app purchase transactions. The only case where Apple don't take commission is when you are selling things that are non used within the app - for example, physical goods that are sent to the user, as in a supermarket or food delivery app. But in those cases, you need to provide your own payment processing; you can't use In-App Purchase. You may want to argue that "tipping other users" falls outside the "used in the app" definition. I don't know about that. It may depend on what the other users are doing that deserved tipping. For example, I guess you can tip your Uber driver and not pay Apple. But it is that aspect that matters, not whether the app is initially free or paid. Note that in many cases the commission will be 15%, not 30%. “On the iOS, iPadOS, watchOS, and macOS App Store, Apple charges a 30% fee for apps and in-app purchases. However, the fee doesn't apply to free apps.” Where does that quote come from? Do read your developer agreement! It has all the answers.

It's not actually an invoice but a Payment Receipt (because, as others have noted, an invoice would go in the opposite direction) No, both invoices and receipts are generated by the supplier and given to the customer. We are the suppliers, Apple is the customer.

Is changing these lines of code to include "void" the best solution? Yes. Or remove -Werror.

I think you should be considering DynamoDB vs. “MemoryDB for Redis”. The important question is whether DynamoDB is fast enough for you - are you trying to update the positions of things in real-time? And you’ll also need to consider cost. DynamoDB is not particularly difficult to use, but you will have issues around authentication/authorisation if you want to connect directly from your app; how do plan to do that? (I’ve only used DynamoDB from AWS Lambda functions that the app invokes.)