Public Builder User Reference

Welcome, Public Service Users!

If you are coming from public.swaplab.net, please note that the UI structure is fundamentally the same as our Private Builder. Most build failures on the public service are caused by simple UI configuration mismatches. Use this troubleshooting guide to resolve common compilation errors.

error_outline 1. Framework Mismatch (Build Fails Immediately)

The Problem: You selected "Capacitor" in the UI dropdown, but you uploaded a Cordova .zip project (or vice versa). The build engine immediately fails because it cannot find the expected configuration files (e.g., looking for capacitor.config.ts but finding config.xml).

The Solution: Ensure your selected UI option perfectly matches the source code you are providing.

menu_book Read about Project Framework Type menu_book Read about Project Source Code
warning_amber 2. Gradle or Node.js Version Mismatch

The Problem: Your build fails during the Android compilation phase (Gradle sync/build errors) or during npm install due to incompatible dependencies.

The Cause: You selected a Reference (Image Tag) that uses a toolchain too new for your project. Each image version strictly dictates the Gradle and Node.js versions used. For example, if your project's plugins rely on an older Gradle version (e.g., Gradle 8.7), but you select a "v2.x" image tag (which forces Gradle 8.13+ and newer Node versions), the compilation will break.

The Solution: Switch the Reference Tag in the UI (e.g., change from Latest v2.x to Stable v1.0.0) to downgrade the build engine to an environment that matches your project's historical dependencies.

menu_book Read about Reference (Image Tags)
build 3. Post-Install Script Failures

The Problem: Your build fails specifically because a third-party package tries to run a bash script during installation (e.g., node-sass failing to compile).

The Solution: Check your Build Settings. If you turned ON "NPM Script Security", the engine blocks post-install scripts. You may need to disable this setting if your project legitimately relies on those compilation hooks.

menu_book Read about Build Settings