App Store 2.4.2 rejection: Battery, heat, and background workload
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps causing excessive resource use or encouraging unsafe device use.
The app can appear responsive while doing unnecessary work in the background. Guideline 2.4.2 addresses rapid battery drain, excessive heat, damaging resource use, and unrelated background processes, including cryptocurrency mining.
Measure the workload
Ask your developer to inspect CPU use, repeated network requests, storage writes, and activity after the app goes into the background. Include ad libraries and media loops. We’d compare an idle screen with the active feature to find work that continues after it should stop.
Review instructions that could put the device at risk, such as covering it while charging.
Reduce or remove the cause
Stop unnecessary loops, release resources when the feature finishes, and remove unrelated background processing. Limit work to what the user’s task requires. A warning about battery use doesn’t correct excessive processing.
Repeat a measured test on the affected device and record the before/after behavior. Explain which process or instruction changed and how Apple can verify it. For a background-mode-specific rejection, also check 2.5.4.
Messages this guide can help with
App Store 2.4.2 rejection; app store 2.4.2 denial; Guideline 2.4.2; Battery, heat, and background workload
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 2.4.2 Checked 22 September 2026