Likely to be questionedApp Store

Background work is limited to the declared feature and does not drain the battery

The question The app declares background modes. Does the background work stay within the declared feature, with location updates or fetches paced so the battery is not drained? Cite the mode and what the code does with it.

A person or a model answers it from the app's texts and screens; the answer is kept only while the facts it saw are unchanged.

Applies when background_mode:location; background_mode:audio; background_mode:fetch; background_mode:processing

Checked from built, not yet uploaded, on a test track, submitted and in review, published

The rule, in our words

• App Review Guidelines: iPhone apps should run on iPad where possible; apps should not drain the battery or overheat the device, and may not run unrelated background work such as mining; they should never tell users to restart the device or change unrelated system settings such as turning off Wi-Fi or security features. Mac App Store apps have extra packaging and sandbox rules.

Okkok never stores the stores' text. Each item above is our paraphrase, and the link is the page it rests on, verified unchanged by fingerprint on every run.

The other store

• Google adds concrete foreground-service rules for Android 14+ (declared type, permission, Play Console use-case description and demo video); Apple states outcomes (battery, heat) rather than mechanisms. partial
• none on principle; Google names Play Protect specifically. same
• Google permits setting changes with consent and reversibility; Apple bans instructing unrelated settings changes outright. partial

Check your app

pip install git+https://github.com/petresandu-cloud/okkok
okkok audit path/to/app

The report names this rule as apple.2.4.background-power and says what to do, who does it, where, and how it knows.