> I guarantee bad actors would remove unpermitted functionality right before the review, and put it back after.
Outside of a dynamic feature flag setup, this would be trivial to detect as Google and Apple completely control the submission process.
Outside of a dynamic feature flag setup, this would be trivial to detect as Google and Apple completely control the submission process.
This wasn't malware or anything like that, but goes to show limits of automated review.
Right, which is exactly why the OP's suggestion would not work, that Apple should always tell you in advance when they plan to do post-release review.
Go one small step further and disable the offending feature during review only for the next build version and you don't even disrupt existing users.
Developer can change flag and there's little Google/Apple/Amazon can do about it.
Your app can be rejected for talking about off-app payment, but how is a reviewer going to find that if it's talked about in a helpdesk document that's fetched via a HTTP call to a remote server and is temporarily edited to remove that paragraph?