Edit profile details and photo
Driver App can show an Edit control for Driver profile fields when account configuration allows Driver data updates. The profile image is a separate control that can open the device photo library and immediately request a photo save after a selection.
This source-only procedure stops before Edit, the profile image, or Update is selected. It does not change personal information, open a picker, read a photo, update a password, save a phone number, or prove that the running service accepted a profile change.
Availability
For a Driver account, Edit is visible only when the reviewed update-data configuration is explicitly enabled and validation fields have loaded. The displayed fields come from the current checkout/profile validation-field configuration rather than one fixed universal field list.
The profile image remains a pressable photo-library entry in reviewed source even when Driver field editing is not enabled. Do not treat the absence of Edit as proof that photo updates are disabled.
Before you start
- Open Profile and wait for profile and validation-field loading to settle.
- Confirm whether Edit is visible.
- Review only the field labels you need; profile content is PII.
- Do not select the avatar/profile image for documentation or troubleshooting.
- Do not enter or change names, email, phone, passwords, or other personal data in this source-only guide.
Profile navigation can refresh user information. A visible value is the current client result, not guaranteed current server truth.
Complete the task
The admitted task is a pre-action review:
- Verify that the profile is populated rather than loading or in error.
- Identify the configured read-only field labels, masked password display, and available phone presentation.
- Confirm whether Edit is present under the configured Driver update rule.
- Identify the profile image as a separate photo-library control.
- Leave Edit, the image, Update, and all field controls untouched.
If Edit is used outside this guide, the form can show configured fields, password/confirmation, and an enabled phone input. It applies required-field, email, phone, and password-match validation. Cancel clears local changes; Update appears after changes or password input and can request a user update.
Selecting the profile image is not the same flow: reviewed source opens only the photo library, requests a small photo with base64 data, and can request the photo save immediately after a selected asset returns. There is no reviewed camera capture path and no separate Update confirmation for that image request.
Verify the result
The only accepted result is recognition of the current pre-action state:
- profile content or its loading/error state is visible;
- the configured field labels and Edit visibility are understood;
- the profile image is identified as a separate library/provider boundary; and
- no PII, password, phone, image, picker, or save action was used.
Do not verify this guide through a changed profile value, refreshed avatar, toast, local session state, history/log, socket event, job, or provider result.
States and variations
| Visible state | Meaning | Safe next step |
|---|---|---|
| Profile loading | Session/user or form state is settling. | Wait for content or error. |
| Validation error | Field configuration could not be used. | Do not press refresh for evidence; report the error class. |
| Read-only profile without Edit | Driver update configuration does not admit field editing. | Do not bypass it; ask the account/configuration owner. |
| Read-only profile with Edit | Client configuration admits the edit form. | Recognize only; do not edit in this guide. |
| Edit form | Configured fields plus password/phone variants are visible. | Use Cancel without changes if opened accidentally. |
| Field validation message | Local required/email/phone/password rules rejected input. | Do not enter real values to test. |
| Profile image visible or missing | Current user photo or fallback asset is displayed. | Do not press it for evidence. |
| Photo library canceled/error | Picker result did not supply a usable asset. | Do not retry or use camera/another provider. |
| Update loading/result | A profile or photo request may be in progress or settled locally. | Do not repeat; server/follow-ons require owner verification. |
Troubleshooting
| What you see | What to check | Safe recovery |
|---|---|---|
| Edit is missing | Driver account level, update-data configuration, validation-field loading and error state | Do not alter configuration or use another product to force editing. Contact the account owner. |
| Expected field is missing | The current validation-field configuration controls the form. | Report only the field label/category; never paste its value. |
| Profile image opens a library unexpectedly | The image control is independent of Edit permission in reviewed source. | Close the picker without selecting; do not grant permissions or choose media. |
| Camera is not offered | Reviewed source uses the photo library and contains no camera call for profile photo. | Do not open a separate camera app as a workaround. |
| Canceling the picker produces an error/toast | Picker cancellation/result handling can fall through to a missing-image state. | Do not retry; report the provider/result class without file names or device data. |
| A field or photo changed unexpectedly | Update request, local session replacement, profile refresh, and follow-ons are separate. | Do not repeat. Escalate with sanitized time and field category, never PII/media. |
| The profile looks stale | Tab navigation can request user refresh, but visibility does not prove currentness. | Avoid editing and ask the account owner to verify current server data. |
Related guides: View the Driver profile · Review the Driver schedule · Manage sessions