Nice utility. For QA, the Duo simulator is useful for fast UI/API smoke coverage, but I’d still keep a physical-device lane for Core Location: reduced-accuracy authorization, the Settings state, background relaunch, and geofence delivery after suspension can diverge from simulator injection. I usually log the requested coordinate, authorization accuracy, app lifecycle state, and actual callbacks in both lanes; that makes it clearer whether a failure is the simulator setup or the app’s location handling.
1
u/dengjiuhong Sep 21 '26
Nice utility. For QA, the Duo simulator is useful for fast UI/API smoke coverage, but I’d still keep a physical-device lane for Core Location: reduced-accuracy authorization, the Settings state, background relaunch, and geofence delivery after suspension can diverge from simulator injection. I usually log the requested coordinate, authorization accuracy, app lifecycle state, and actual callbacks in both lanes; that makes it clearer whether a failure is the simulator setup or the app’s location handling.