You'll probably be fine. Are you the sort of person who notices when something takes fractionally longer than it should, or have you been using a decade-old computer happily until now? Can you be disciplined and manage storage, or do you need an "infinite" SSD to store all your old files?

Output in iOS 17: http://192.168.1/api/rest/contents/Shan%27s%20iPhone%20%40%24%E2%82%B9/test.jpg Output in iOS 16: http://192.168.1/api/rest/contents/Shan%27s%20iPhone%20%40%24%E2%82%B9/test.jpg Unless I've gone blind, those outputs are identical. So I believe your problem is not with the percent-encoding, which is unchanged, but with something else. One thing to look at: 192.168.1 is not a valid IP address. Also, http: (rather than https:) may be blocked by security features. A more general observation: generally, it's best to do percent-encoding on the individual components of the URL before joining them together. You seem to be taking a complete URL and then trying to encode it. That can work if you know that your query parameters (etc.) have a limited character set, but it doesn't work in general.

See: https://developer.apple.com/forums/thread/732903 This must be fixed. No; it seems to be a deliberate change by Apple, so you will need to stop relying on the old behaviour.

You won't find anything official, as far as I am aware.

I guess you have seen my thread here: https://developer.apple.com/forums/thread/734750

You are NOT running the same commands that the CodeLite GUI is running. We can see the commands that it runs in your screenshots. Run those same commands in the terminal.

flipabit We don't get a lot of discussion of that on this forum. I guess you're more likely to get a useful reply on whatever forum or other support channel they have.

the content itself isn't "truly" protected since it lives in CloudKit's public database. Some things to consider generally, for downloadable premium content: Do you need to worry about bandwidth costs? (Not for CloudKit) Are you obliged to pay the provider of the content even for unauthorised downloads? Is the type of content, or the main market for your app, something that is often pirated?

You need to try to run the commands that your CodeLite GUI is running, which we can see in the screenshots, in the terminal. You still haven't done that.

No.

Despite having received three payments, I'm unable to find any corresponding invoices for these transactions. You are the supplier, Apple is the customer. Apple pays you for the apps. It is YOU who needs to generate invoices, not Apple. clarify whether developers in Spain are required to submit a monthly invoice in PDF format. I don't think so. Apple certainly doesn't care. There are some countries where businesses are required to always supply an invoice; I think Italy is one, or used to be one. The typical story is that you go to Italy on holiday, and when you leave a restaurant you leave the paid bill on the table; the waiter then runs down the street after you to give you the bill that you have forgotten, in case a "financial policeman" asks you for it. I don't think this ever happened in Spain, so I guess that you don't need to do this.

Have you hard-coded the app version in your receipt checking code, and the app version has of course changed in the updates?

I've gathered it isn't your Unit purchased * the price of your app - Apples commission. It is basically that though you have to consider tax (VAT) and exchange rates. The simplest answer is, you get the "proceeds" shown in the tables, converted to your currency on the day you receive the payment from Apple.

Can't you copy and paste, rather than posting screenshots with the scrollbar moved? Anyway, we can now see all of the command that it is running (I think). What happens when you run that from the terminal?

Were you asking about these? No. I'm asking about what I can see in one of the screenshots that you posted. It shows the command that the GUI tool has invoked. It starts /usr/bin/g++ -c. I can't see all of it because there is a scrollbar and some of it has not been captured in the screenshot.