Skip to main content
If an app behaves unexpectedly, first identify whether the problem appears in the preview, the published app, or both. That distinction matters because the environments have separate data and secrets behave differently.

​
Give the chat a reproducible problem

Include the screen, action, expected result, actual result, and whether it happens every time. Use a synthetic record and remove personal information from screenshots or error messages.

​
Check common causes

  • Changed preview, unchanged live app: publish the version you intend to share.
  • Missing records after publishing: preview and live databases are separate.
  • Integration fails in preview: environment secrets are supplied to the published app, not preview.
  • Feature differs by plan: review pricing and plans and credits.
  • Domain is not ready: review the setup status and custom domain guide.

​
Contact Fabricate support

Email support@fabricate.build. Include the affected project or published address, when the issue happened with your time zone, and the shortest steps that reproduce it. Say whether the issue affects preview or the published app. Do not send passwords, API keys, recovery codes, payment card details, or private customer records. Describe a secret by its configuration name, never its value. Support instructions do not require you to make a private app public. For your own app’s users, provide an appropriate support contact in the app itself. Your users should know who operates the app and where to report a problem.