Built-in device capabilities that Apple provides for free, such as the flashlight or basic camera access, can't be repackaged as a paid feature within your app — monetization has to be for something you've actually built, not a paywall on the OS itself.
A recurring pattern with "utility" apps that lock a trivial OS-level feature, like toggling the flashlight, behind a subscription.
"Your app charges users to access a feature that is otherwise freely available on the device, per guideline 4.10."
Guideline 4.10 says a developer cannot charge for capabilities that the device already provides for free. Basic functions such as the flashlight, simple camera access or other built-in features cannot be repackaged and put behind a payment as if the app had created them. Monetisation is expected to be for something the developer has actually built.
Customers already own their devices and the features that come with them. Selling access to those features as if it were an app's own value misleads people and can extract money for something that costs nothing. By requiring that paid features add real value, Apple keeps the Store from filling with utilities that only wrap a toggle in a paywall, which tends to attract complaints.
Yes, when it provides functionality beyond what the device offers.
They are related, but 4.10 is specifically about paying for built-in capabilities.
Added value on top of the camera can be monetised, but not basic access.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.