I think you misunderstand app review. They do about 4 things, in my experience: ”Virus scan”-type analysis of the app to see if you have included anything naughty. Not a problem except when they have false positives. An automated analysis of your app metadata to see if you mention Android or anything else they don’t like. They run the app once to see if it crashes on launch. If you have in-app purchase they will try to make sure that they work. Just submit your app and see what happens. If they reject it, don’t try to “communicate” or “document”, just do exactly what they tell you to do and resubmit.

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0053r7.pdf links to an example implementation: https://github.com/PeterSommerlad/SC22WG21_Papers/tree/master/workspace/p0053_basic_osyncstreambuf I've no idea if it is usable, I've never tried to use syncstream myself.

That was mostly the weekend, right?

I think you need this: https://developer.apple.com/documentation/storekit/product/subscriptioninfo/status/3851115-updates Get that async sequence for your subscription group using this: https://developer.apple.com/documentation/storekit/product/subscriptioninfo/3822297-status I think you get an update when it expires. Please let me know if you get this to work, I will need to implement something like this soon.

Pretending to be older than you are (and borrowing your mum’s purse) is as old as the hills. Whether it is “still a thing” - well, you’ll have to ask a young person. Oh hang on….

It's not third party. It's not related to 'Privacy Manifest'.

It works for me without any extra code.

Is this an intended behaviour? No. Show us your code.

You'll find lots of similar posts on this forum if you can guess the right words to search for. There is no magic solution, you just need to keep waiting. Actually, you've only been waiting two weeks; in the past there have been some much much longer delays!

Apple don't publish any such specs.

Your equation for FSPL is not in dB. You need either 10 log_10 or 20 log_10 of that value. Whether it's 10 or 20 depends on whether it's in mV or mW. Also, I think the f term should disappear. I think it's because there is some sort of assumption about the antenna size being related to the wavelength, or something. I guess you've already looked at the Wikipedia page, but if not: https://en.wikipedia.org/wiki/Link_budget Please let us know if you get anything like useful numbers from this. My experience has been that it really doesn't work in the "real world". I have a simple weather station in my garden which sends data to a receiver in a cupboard the house and I log the RSSI. It's in the same frequency band as bluetooth. It varies dramatically depending on, for example, whether blinds are open or closed in other rooms, whether the ironing board is in that cupboard, where the metal gardening tools are in the garden, and so on.

I do have the check for access in the code as well as the info.plist entry No, you should check only in the code (at runtime). Remove the UIRequiredDeviceCapabilities item from the info.plist.

No.

Does it say “carried forward” or something to that effect? I think you need to contact Developer Program Support.

To me that is saying that I cant add new features to an app that requires additional permissions. Is that correct? Not quite. The app needs to check at runtime for the feature and provide the app’s other functionality even if it is not present.