Build Modes

Every build Primio produces runs in one of two modes: Release or Debug. You can set the mode independently for each platform — so you can debug your Android build while keeping Web and iOS on Release.

The setting lives in Workspace → Build Mode.

Release vs Debug

	Release (default)	Debug
Purpose	Production-ready builds	Troubleshooting issues
Code optimization	Minified and tree-shaken	Unoptimized, full source
Assertions	Removed	Enabled
Logging	Minimal	Verbose, detailed errors
DevTools	Not available	Supported
Performance	Fast, small file size	Slower, larger file size
App store ready?	Yes	No

All platforms default to Release. You should only switch to Debug when you need to investigate a specific issue.

When to use Debug

Debug mode is a troubleshooting tool, not a development mode. Use it when:

• Your app crashes on a real device but works in the preview
• You need detailed error messages or stack traces from a native build
• You want to inspect app behavior using Flutter DevTools

Once you’ve identified and fixed the issue, switch back to Release before building for distribution.

Keep Release as your default

Release builds are smaller, faster, and required for app store submission. Only switch to Debug when you’re actively investigating an issue — and switch back as soon as you’re done.

How to change build mode

1. Open Build Mode

   Go to Workspace → Build Mode. You’ll see all five platforms listed.

2. Toggle the mode

   Click Debug or Release next to the platform you want to change. The change takes effect on your next build for that platform.

3. Build as usual

   Go to Workspace → Publish and start your build. Debug builds show an amber DEBUG badge in the build history so you can tell them apart.

Platforms

You can set build mode independently for each platform:

• Web Preview — the live preview in your workspace
• Web Publish — free PWA hosting
• Web Export — downloadable PWA source files
• Android — APK and AAB builds
• iOS — IPA builds

Platform-specific notes

Android: Debug builds are rejected by Google Play

Google Play does not accept debug APK or AAB files. Always switch back to Release before building for Google Play submission.

iOS: Debug builds may fail App Store validation

Debug IPA files may not pass App Store Connect validation. Use Release mode for any build you intend to distribute via TestFlight or the App Store.

Web: Debug builds produce larger files

Debug mode disables minification and tree-shaking for web builds. The resulting files are significantly larger than Release builds. This affects both Web Publish (hosting) and Web Export (download).

Web Preview: Debug banner

When Web Preview is set to Debug, a debug banner appears in the preview. You can use your browser’s built-in DevTools to inspect the app.

Next steps

• Debugging & Fixing Errors — common issues and how to resolve them
• Android Builds — build APK and AAB files
• iOS Builds — build IPA files for TestFlight and the App Store