Reported during QA session. Proposal.
What's wrong
The debug panel is only reachable from deep inside the authenticated app — Settings → Support → About, via a hidden tap gesture on the version. That means every debug capability is unavailable exactly when a tester most needs it: before or during login.
QA cannot reach the fixture login-as shortcuts, environment/server configuration, or auth diagnostics without first completing a successful login by hand, which defeats the purpose of the login shortcuts and makes login-related failures much harder to investigate on a device.
What I expected
A tester should be able to open the debug panel from an unauthenticated screen and use the login-as fixtures and environment tooling to get into the app.
Proposed change
- Add a debug panel entry point to an unauthenticated screen (login or the getting-started screen), using the same hidden-gesture pattern already used on the About screen so it stays invisible to real users.
- Keep it behind the existing debug build flag, so production builds are unaffected.
- Ensure sections that require an authenticated session degrade gracefully rather than erroring when opened while logged out.
Steps to reproduce
- Install a debug-enabled build and launch it while logged out.
- Try to reach the debug panel from the login screen — there is no entry point.
- Note that reaching the panel requires logging in first, then navigating to Settings → Support → About and tapping the version.
Additional context
The panel's auth section already exists to log in as QA fixture accounts, which is the capability most obviously wanted from a logged-out state.
Related: the QA build flag not being set in the preview profile is tracked separately (#278) — that must be resolved for this to be usable in preview builds.
Reported during QA session. Proposal.
What's wrong
The debug panel is only reachable from deep inside the authenticated app — Settings → Support → About, via a hidden tap gesture on the version. That means every debug capability is unavailable exactly when a tester most needs it: before or during login.
QA cannot reach the fixture login-as shortcuts, environment/server configuration, or auth diagnostics without first completing a successful login by hand, which defeats the purpose of the login shortcuts and makes login-related failures much harder to investigate on a device.
What I expected
A tester should be able to open the debug panel from an unauthenticated screen and use the login-as fixtures and environment tooling to get into the app.
Proposed change
Steps to reproduce
Additional context
The panel's auth section already exists to log in as QA fixture accounts, which is the capability most obviously wanted from a logged-out state.
Related: the QA build flag not being set in the preview profile is tracked separately (#278) — that must be resolved for this to be usable in preview builds.