captured using an exception handler and displayed using NSAlert. Don't do that; let the app crash, and then look at the crash logs that Apple will send you. These will include a stack trace so you'll have some chance of identifying the cause. If you really want to trap fatal exceptions yourself, include more diagnostics.

See this thread: https://developer.apple.com/forums/thread/739568

I've read up on Bonjour and on the Network framework and it appears to me (and I may be wrong) that these capabilities only support either devices on the same local network, or devices that are in close proximity to one another. Correct. This is a hard problem in general. As well as the things you’ve mentioned, you need to consider NAT. Have a look at this to get started: https://en.wikipedia.org/wiki/STUN The difficulty of true peer-to-peer communication on the Internet leads many to use a centralised server or some other alternative.

Sadly, in most cases, the best approach is to write entirely separate apps for each platform.

Based on other posts here, new dating apps seem to be entirely banned.

does anyone know if the 15% cut we qualified for in 2023 was only for the US?Meaning that Canada and Europe would stay at the 30% revenue share? It applies to all sales. If you seem to be receiving less than you expected, it’s probably because you have not allowed for tax.

Must I really raise an official support ticket to get an answer to this? You could try that, but (a) they probably won’t be able to reproduce it, and (b) if they do reproduce it, they’ll say “That looks like it might be a bug. Please report a bug. Thanks. Bye.”

iOS17, the US region/locale now uses a` UTF8 NARROW NO-BREAK SPACE You are not the only one to encounter obscure bugs with this as the root cause: https://developer.apple.com/forums/thread/732993

Do you ever run ANALYZE ?

@endecotp you shouldn't place key_id in files that can be backed-up, cause corresponding app attest private key doesn't migrate to new device. Right, so where should I put it?

There is nothing you can do. Just keep waiting.

I believe the TestFlight review is possibly just a virus-scan, or similar. Just submit and see what happens. Apple owns the 17...* IPv4 range. You could consider adding this to your IP filter.

I mentioned this in another thread: https://developer.apple.com/forums/thread/744803 I wasn't aware of manageSubscriptionsSheet. What does it actually do? The docs have literally no description: https://developer.apple.com/documentation/swiftui/view/managesubscriptionssheet(ispresented:)/ https://developer.apple.com/documentation/swiftui/view/managesubscriptionssheet(ispresented:subscriptiongroupid:)/

Which mode uses the least battery? I think they are all probably very similar; they all use the same hardware, but do different software processing of the results IIUC. I would gladly trade battery performance for less frequent updates. My understanding of how the GPS hardware works is that the radio needs to be continuously on, whatever the update rate. Unless you want very infrequent updates, e.g. every ten minutes or less?, the energy cost is much the same. Maybe. I would use default and expect the OS to do the right thing. You might be disappointed. For example, “default” snaps to where Apple Maps thinks road centerlines are.

See also: https://developer.apple.com/forums/thread/745132 They suggest it is related to accepting an updated developer agreement.