At the end I removed my app from the EU market. Does this permit you to not supply your pone number (etc) to Apple?

You need the "App Store Connect API". (Search for it.) Beware, it's not easy to use.

Your choices include Buy more devices. Cheap ones from eBay, even with broken screens, are OK for screenshot generation. Borrow devices from friends. Fake the bluetooth communication so you can use the simulator (e.g. as Claude31 suggests). Fake the screenshots, by scaling the ones that you already have to the required sizes.

Do you specifically need "always on" location, rather than "when in use"? Have you sufficiently demonstrated in your video that "when in use" is not sufficient?

<string>Our app does not use this api directly but (apparently) an included framework does</string> No, that field is not supposed to be a human-readable string. It's supposed to be one of Apple's "reason codes", which look like AB12.3.

OK. That’s not going to get you in the search results. There must be thousands of recipe apps; only ones that already have the best sales, most 5* reviews etc. will appear in the non-paid part of the search results. In 2024, you cannot rely on users just finding your new app in the App Store by searching for a very generic unpaid keyword like “recipes”.

If you can’t find the answer in an ifixit teardown, the answer is not available. I would guess they are custom parts, or at least custom variants, made specifically for Apple. Why exactly do you think you need this? Is it too late to change your dissertation subject?

How much are you paying, compared to the recommended bid for ”recipes”?

I'm an indie/hobby developer that has a paid for app that doesn't sell many units (only 40 in the 3+ years it's been available) The important consideration is whether this is your “trade, business, craft or profession”.

Does OpenGL require special permissions? No. Superficially your crash looks like memory allocation for a texture, but that may or may not be the real cause. Have to tried to allocate something ridiculously large?

How can I solve this ? Find some other way to store this data, e.g. in the filesystem.

Yes, this happens to me. No, there is nothing that you can do to fix it. When I get “Apple Support told me to contact you”, I always ask them to forward the email to me, or if it was a phone or in-store conversation to share the name of the person they spoke to and the date/time, “so that I can lodge a complaint with Apple about that employee”. Of course I don’t have any way of lodging such a complaint, and no user has ever replied with the requested info, but I believe it makes it clear to the user that I’m serious about Apple being wrong.

the Release build of the Swift version was a little faster than the Release build of the C++ version Would you like to share your C++ version? And maybe a test harness? I love a challenge. For large values of 5, it's better to sort the two strings to do the weak-hit tests. For small values of 5, nested loops will be just as fast in practice. 700X for debug is a bit surprising. Maybe there is something else going on. Perhaps a Swift expert will comment.

You can use the App Store Connect API. It is massively more complicated than just uploading a CSV file, unfortunately.

The receipt is always present in production. In development, it's present if you have done any IAP activity, or anything else that makes it appear, but otherwise it is not present. Does this explain what you are seeing?