Understand startup and loading
When you open Driver App, a full-screen loading view can remain visible while the app prepares the current session and determines which startup surface can appear next. Treat this as a readiness state, not as confirmation that a network request, permission, notification setup, or later driver action succeeded.
Availability
This state can appear whenever Driver App starts. What follows depends on the configured app, saved tutorial and session state, the driver's schedule, device permissions, platform behavior, connectivity, and notification setup.
The app can continue to a signed-out or authenticated surface only after its local startup gates report that they have settled. Some gates can involve an operating-system prompt or external service; those handoffs have separate results and ownership.
Open this capability
- Open the installed Driver App for your Ordering project.
- Keep the app in the foreground while the loading view is visible.
- Respond only to a clearly labeled device prompt you understand. A prompt is a separate permission or provider gate, not proof that startup completed.
- Wait for the app to present a signed-out entry, schedule gate, authenticated workspace, or another visible startup state. A tutorial may appear; this guide does not guarantee that a clean first launch will reach it.
The loading view does not offer a retry or navigation control. Do not tap the screen repeatedly or assume that leaving the loading view proves every startup dependency succeeded.
What drivers can understand
The next visible surface tells you which local startup branch the app selected:
- a tutorial may appear, but this guide does not guarantee it on a clean first launch;
- a signed-out entry leads toward the configured sign-in experience;
- a schedule gate means the authenticated account has a configured schedule prerequisite;
- the main driver workspace means the app admitted the authenticated navigation shell.
These states do not confirm that an order, assignment, location update, notification, message, or other operational effect succeeded.
States and variations
| Visible state | Source-defined condition | What to do next |
|---|---|---|
| Loading view | Navigation readiness or the app's local permission check is still loading. | Wait for the next visible surface. |
| Tutorial | The tutorial became visible, but this guide does not guarantee it on a clean first launch. | Follow only the controls that are actually visible and report a blocked or repeating transition. |
| Signed-out entry | The app is signed out and the tutorial does not take priority. | Continue with the visible sign-in experience. |
| Schedule gate | A signed-in driver has schedule validation enabled and the current schedule check blocks entry. | Review the visible schedule prerequisite before continuing. |
| Authenticated workspace | The signed-in path has passed the current local startup gates. | Choose the task that matches the visible order, map, message, or account area. |
| Device or notification prompt | The operating system or notification provider is requesting a separate decision. A permission-specific app surface can also appear later when the Driver opens the map. | Read the prompt and the permission guide; do not treat dismissal or acceptance as app readiness. |
Startup behavior can differ between iOS and Android because permission and notification handling are platform-specific. A background-to-foreground transition can also trigger separate refresh work after the initial screen has appeared.
Troubleshooting
| What you see | Likely boundary | Safe recovery |
|---|---|---|
| The loading view remains on screen | One or more local readiness flags have not settled, or startup was interrupted. | Check connectivity and look for an operating-system prompt without changing unrelated settings. If the state persists, record the platform, app version, time, and visible screen without personal or operational data, then contact your app operator. |
| The tutorial appears again | The locally stored tutorial state did not disable the configured first-run branch. | Complete the visible tutorial once. If it returns, report the visible behavior without sharing account data. |
| You reach sign in instead of the driver workspace | The app selected a signed-out session state. | Use the sign-in guide. Do not repeat a prior operational action or infer that the account was signed out by the server. |
| A schedule gate or device prompt appears | A configured account or device prerequisite has priority. | Follow the matching guide rather than trying to bypass it. |
| Startup advances but expected content is unavailable | Navigation readiness and content availability are separate. | Use the guide for the visible area and verify its loading, empty, unavailable, or error state. |
Related guides: Driver App overview · Sign in as a driver