Distinguish a blank application from an empty record list. An empty list can be valid when a contact has no visible records; a blank screen during startup usually needs a different investigation.
Check startup logs for Firebase initialization failures and config-request errors. Verify the Firebase application settings and public API URL. The current entry point initializes Firebase before starting the Flutter interface.
Confirm that the records belong to the authenticated customer and are visible to that contact. Check permissions, project visibility settings, hidden drafts, and contact-only ticket rules. Compare against the customer web portal, not just the administrator’s CRM view.
Clear search/filter selections and reload the list. If a feature is permission-restricted, changing its menu visibility is not a valid fix.
Check for an API parsing error or mismatch between mobile and module versions. Invoice statistics may arrive as strings while monetary values are numbers; custom model changes must follow the API contract rather than assuming all numeric-looking fields have the same type.
Capture the screen name, safe record identifier, request path, status, and sanitized error. Avoid attaching complete financial documents or customer data to public support requests.
For a regression after customization, reproduce the same workflow in a clean copy of the matching release.