Understand force-status prompts
The Driver App source contains force-pickup and force-delivery forms intended to collect a reason after a normal status attempt encounters a location-area error. These forms are conditional recovery prompts, not ordinary delivery actions.
Availability
A force-status form can open only when the client recognizes a specific error result from an earlier pickup or delivery status request. The reviewed client contains the matching branches, but the accepted API source does not prove that the running backend emits those exact fragments in the required shape.
Do not expect a force prompt to appear, and do not treat its appearance as proof that forcing the status is supported, authorized, safe, or eligible.
State and result matrix
| State | Client behavior | Safe interpretation |
|---|---|---|
| Normal status request has not failed | No force prompt | Use the standard owning procedure only |
| Generic or differently shaped error | Standard error state | No force-action eligibility |
| Recognized pickup-area fragment | Client can open the force-pickup form | Conditional client branch only |
| Recognized delivery-area fragment | Client can open the force-delivery form | Conditional client branch only |
| Form open | Reason menu, required comment, location checks, and possible image/code fields | Pre-action form; no backend acceptance |
| Empty comment | Final action disabled | No request |
| Location issue | Requirements Not Met or an error can appear | Do not bypass; location correctness is unproven |
| Image required | Photo area and disabled final action | Media/provider boundary; no proof claim |
| Security code shown | Client-side delivery code field | Not secure/server-validated proof |
| Submission error or unchanged order | No confirmed status | Close, refresh, and verify with a dispatcher |
What the forms collect
Both force forms can show:
- a reason menu;
- a required comment field;
- configured location checks for pickup or delivery;
- a required status image when configured; and
- for some force-delivery configurations, a Security code field.
The comment is checked only as a non-empty client value, and the reason selection is optional in the reviewed payload. Neither field proves server validation.
The reviewed force path does not establish complete, correct, or trusted location data. Supplied location also lacks separate freshness and mock-policy evidence. A visible force prompt, location check, comment, image, or code therefore does not establish correct location or secure authorization.
Platform, permission, and lifecycle behavior
Opening the form passes through the Driver App permission aggregate and mounts a GPS-capable form. Permission prompts, Settings, GPS, camera, keyboard, and code focus can differ on iOS and Android.
The underlying standard order detail can already be reading and following location. No platform or lifecycle state turns the force prompt into a proven server-approved action.
Effects and boundaries
If a force-status request were submitted, pickup and delivery target different statuses and can affect order history, messages, reporting, Driver/location state, logistics, realtime events, notifications, mail, webhooks, jobs, images, and providers. Some effects can settle separately or fail without rollback.
This reference does not provide a force-status procedure. When a prompt appears, stop and follow your organization's dispatcher or support process before any submission.
Troubleshooting
- If no force prompt appears, do not retry the standard status merely to trigger one. Review the original error and contact a dispatcher.
- If a force prompt appears unexpectedly, close it and refresh the order before continuing.
- If location is missing, outdated, or rejected, do not enter or share coordinates manually and do not treat an image as a location substitute.
- If the form requests a code, do not guess, reconstruct, or share it in chat or support notes.
- If the final status is unclear, reopen the order and ask a dispatcher to verify the current state. Do not submit the force action repeatedly.
Related guides: Complete pickup · Complete delivery · Pickup problems · Delivery problems · Location permissions