Android 17 Real Device Testing: A Practical Guide

Android 17 introduces breaking changes that emulators will not catch. If your CI pipeline runs exclusively on virtual devices, you are shipping blind. This guide covers what changed, what breaks, and how to build real-device Android 17 coverage into your automation workflow before it becomes a production problem. What Changed in Android 17 That Breaks Tests Android 17 ships several behavior changes that directly affect test outcomes on real hardware: Background process restrictions: The OS enforces tighter limits on background execution. Apps relying on WorkManager , AlarmManager , or foreground services need re-validation under the new limits. Permission model updates: Location, camera, and health data permissions now use restructured dialog flows. Any UI automation touching permission grants needs updated selectors and assertions. Predictive back gesture enforcement: The system-level back gesture is now more strictly enforced. Deep link navigation and onBackPressed() overrides behave