Now Developer Program Support have told me to contact Developer Technical Support - ID 1634088....

This isn't fixed, after 3 months. I'm just looking at another documentation bug which I reported in July 2022 (FB10566903) that hasn't been fixed. Did the developer documentation team all get fired, or something? Come on Apple. We need the documentation to be accurate. It's really difficult to write code when we can't be sure if the bug is in our code, your code, or your documentation.

Wow! I’m the guy who said “I sympathize” and tried to suggest what you need to do. Now you’re attacking me too! There are over 370,000,000 folk in this country and you are only ONE. Wrong, as it happens. I live in Scotland. Bye!

Note that this forum doesn't send email notifications when you post comments; it's better to always post replies. The request to see a video is a good sign. If you submit an app that requires external hardware to operate, they will either ask you to send them physical hardware, which they won't return, or they will ask you to send a video. I once had to send a demo video of an app that included bluetooth communication. This is by far the better option of the two. You don't want to have to send them a new controller each time you submit an update. Don't expect to get very far with your "liar" / "assault" accusations. I know it's difficult, but try not to take it personally. It's only an AI bot that's sending you those messages. Gamers typically hate written instructions so they rightfully assume a Computer Game requires a Controller.  I disagree. iPad owners don't read the app description so they assume an app they've downloaded will just work when they poke the screen with their finger. The situation may be a bit different with Apple TV, but your app is for both, right? I don't think I've ever seen anyone use an iPad with a game controller, ever.

I sympathise, but beware that if App Review do not read that far through the description then end-users most certainly won't. You'll end up with a lot of 1-star ratings with the same complaint that "nothing happens". Especially for a free app, users will look only at the app name and the icon and the rating and not much else. Does the app present a "No controller detected" error message? What do other app do?

I've had a reply from Developer Program Support. (Case 30000000852971.) They have just directed me to the documentation that I've already read. I've asked them to escalate it. Has anyone else made any progress?

Welcome to the amazing world of spherical geometry! It looks to me as if they may be using “web mercator” internally; this has trouble between +/- 85 degrees and the poles. @Leafboats, can you check what the boundingMapRect is for the MKCircle in your first screenshot? It looks to me as if the circle should extend beyond the north pole; I suspect the boundingMapRect is clipped at 90 degrees North. This would be a problem even if they weren’t using web mercator. (I see that MKMapRect has some special handling for rects that cross -180 degrees longitude, but doesn’t seem to have anything similar for the poles.) Wouldn’t life be easy if we lived on a flat earth!

Are you sure of 'An iOS app cannot act as a Bluetooth Classic device'? Let's say I'm 85% certain. The 1812 service can't be added successfully to the client device, so host device is not able to find this service. I got this error: peripheralManager didAdd service name: , uuid: 1812, error: Error Domain=CBErrorDomain Code=8 "The specified UUID is not allowed for this operation." UserInfo={NSLocalizedDescription=The specified UUID is not allowed for this operation.} Right, it does look like they have specifically blocked this UUID. Question: have you found any other App Store apps that act as Bluetooth keyboard/mouse? According to (a link which I'm apparently not allowed to copy and paste, shitty forum software) , we found classic HID service a 1124. I succeed when I try to add service 1124 to peripheralManager. But this host device doesn't connect it as a HID device. I think here iOS system treat 1124 as a custom service over BLE, not over Bluetooth Classic. Yes, exactly.

To add another complication, I get different behaviour when I connect to the iPhone or iPad over USB and view the app's files with the Finder: iPhone, Files app: doesn't view app's documents at all. iPhone, Finder over USB: views the app's documents but won't open folders. iPad, Files app: views the app's documents including contents of folder. iPad, Finder over USB: views the app's documents but won't open folders.

An iOS app cannot act as a Bluetooth Classic device. What error do you get when you try 1812? (Edited to add: if you could get BT LE 1812 to work on the iPhone, are you sure that the host device would understand it? I don’t know how common it is.)

we contacted and tried to verify the email Beware, in my experience Apple Support cannot reliably distinguish between spam and emails sent by other parts of Apple.

Does your app include this web server and a webview in the same process? If it does, you can hack the webview to change 127.50.100.1 to 127.0.0.1. There is a delegate method that is called when the server sends a redirect. (IIRC) Then you don’t need to update your corporate server.

I remember your previous thread. Based on that, I can’t understand why you are now considering using OpenGL. Do you care about portability to other platforms, or the web?

I actually formed a limited company specifically so that I would get a company name in the app store, rather than my personal name. Of course as soon as I did that, Apple stopped showing the developer name under the app name in the app store, and instead show a new "subtitle" or "promotional text".... The result has been an increase in bureaucracy in my life and zero change in sales.

I think that's only possible on a jailbreaked phone, isn't it? But my impression is that it becomes very hard to jailbreak the recent IOS releases, so I take it for granted that app data files can't be accessed by others in iOS. I've not been following this subject, but likely your opponent will be slow to install new iOS versions! This is one reason for keeping your app's required iOS version recent - but that harms genuine users with old devices. Another question. If what you said is true, is it a common practice to encrypt app data files? I don't know how common it is. I do encrypt some data files for which I pay a royalty to a third party; I do that because I imagine standing up in court when they sue me for not looking after their valuable data, and having to tell the judge that I could have encrypted it but didn't. There are two standard problems with that - what do you do with the keys, and how do you prevent the user from capturing the data when your app presents it to them (especially if it's e.g. video). There are actually two slightly different problems, one for data files built in to the app and the other for data files that the app downloads from your servers when it runs. Embedding a fixed decryption key in the executable has some chance of working.