Build and runtime problems

Check a Web Viewer app in three stages: its project checks, its production build, and its behavior inside FileMaker Pro. A browser preview does not prove the FileMaker Web Viewer path works.

The project checks fail

Ask the coding agent to run the checks defined by the app and fix errors in application source. Common causes include stale generated types, an API changed by a JavaScript library update, or an import that exists only in the local development environment.

Do not edit vendored or generated files to suppress an application error.

The production build fails

The production build must finish before ADT can place the app in FileMaker. Ask the agent for the first build error, fix that source or configuration problem, and run the checks again. Later errors often follow from the first one.

ADT cannot place the app in FileMaker

Confirm the app is registered in adt.json, bound to the intended FileMaker file, and has a completed production build. Then ask the agent to diagnose the live FileMaker connection and run Deploy to FileMaker.

The FileMaker operation stores the app source in persistent data. A successful build alone does not change the copy held by FileMaker.

The app works in a browser but not in FileMaker

Test the failing feature inside FileMaker Pro. Check script calls, record access, navigation, and the account's privileges. Browser preview uses the development bridge; a FileMaker Web Viewer provides its own FileMaker JavaScript context.

If the Web Viewer is blank, collect its console error through the coding agent and confirm that the stored app source is current. If FileMaker calls hang, follow Components and Web Viewer connection problems.

See Test an app in FileMaker for the verification checklist.