Off: routine Gradle wrapper setup is build preparation, not a repair. On: also flag/export wrapper-only changes.
Reuse a ZIP already stored in App Builder
Recent Source Archives
⚙ Scanning archive for build targets...
Choose Build Type
Choose Project
Windows Output
Build Flavors
APP PROFILE▼
App match
Keystore
Scheme
Separate aliases with comma, semicolon, or |. Target name/package matches are preferred over the shared ZIP filename.
Windows Authenticode certificate only; Android keystores cannot sign EXE/MSI files.
Sign APK with keystore
Keystore ProfileSelect a profile▼
No keystore profiles yet.
🪟 Windows Authenticode signingUnsigned development build▼
No Windows signing identity selected. Executable will be marked unsigned.
This selection signs the current Windows build. To remember it for this application, save it under App Profile → Linked Windows Code-Signing Certificate.
Active Builds
▼
Build Library
▼
All words must match
No builds yet. Pick a project .zip and start a build.
⚙ Settings
Automatic Source Repairs
Repair mode: Safe only · Max two distinct attempts per upload. The original ZIP, app version, signing and security settings remain unchanged.
Real source corrections (dependency conflicts, incompatible Gradle configuration, supported manifest/resource fixes) are always reported when successful. This preference affects future builds and the display of historical wrapper-only repairs. It never deletes stored artifacts.
Windows Code Signing — EXE / MSI
Windows requires an Authenticode Code Signing certificate; Android .jks files cannot be used. This Linux server supports an exportable .pfx/.p12 identity through osslsigncode. Hardware-backed and Microsoft Artifact Signing need a separate signing integration. A signature does not guarantee Norton or SmartScreen reputation.
🔐 Remember this browser for Windows signing
Checking browser authorization…
The Docker administrator token is needed only once per browser, not for each build. Certificate passwords remain server-side and are not login passwords.
Checking Windows signing backend…
Add a Windows certificate profile
Available Windows Signing Profiles
Signing is never automatic until you explicitly choose a Windows profile for the build. If signing, timestamping, or verification fails, the build fails and the unsigned executable is not published as a signed release.
Why Norton/SmartScreen may warn even when signed
Authenticode integrity, certificate-chain trust, and file/download reputation are separate checks. A self-signed certificate can correctly sign an EXE while remaining untrusted by default on other PCs. A public code-signing certificate does not guarantee warning-free distribution. Never disable security software to conceal a warning.
If Norton incorrectly flags a tested release, submit it for review at Norton false-positive submissions. Include the detection name, alert ID, file name, version, and SHA-256 from the release manifest; review the file before sharing it with any third party. No file is uploaded automatically.
Verify on Windows (PowerShell 5.1)
$exe = "$env:USERPROFILE\Downloads\YOUR-APP.exe"
Get-AuthenticodeSignature -LiteralPath $exe | Format-List Status,StatusMessage,SignerCertificate
# If Windows SDK SignTool is installed:
signtool verify /pa /v "$exe"
Valid = Windows accepts the signature under current trust policy. NotTrusted/UnknownError may indicate an untrusted self-signed root; NotSigned means no recognized signature. Linux build verification cannot assert Windows trust. For internal/test certificates, use the public-certificate export and opt-in trust instructions after checking the exact SHA-256 thumbprint.
One rule controls what App Builder keeps. Purging a build removes the finished artifact(s), matching source ZIP + JSON, build log/history, and any APK .idsig companion together.
Display only. When off (recommended), every build retained by the policy above is shown as its own Library tile, including repeated builds with the same version/build number. Turning this on hides older retained tiles but does not delete them.
Advanced: limit policy to selected projects
Deletion is intentionally paired. App Builder will not keep a completed source ZIP after its retained build is purged, and deleting a Build Library entry also removes its matching source. If another retained build still uses the same source ZIP, that shared source is preserved.
▶
Storage Health & Cleanup
Find stale Processing workspaces and source/build pairs that no longer match. Active builds and Not Built sources are protected.
An orphan finished artifact is a file no longer referenced by build history or an upload JSON. A built source is orphaned only when its JSON records finished artifacts and none of those artifacts exist. Pending/failed sources in Not Built are never removed by this cleanup.
▶
Builds / Finished Artifacts
Finished outputs grouped by extension and project. APK .idsig signatures stay beside their APK and are shown as companions, not separate builds.
▶
Uploads / Source Archives
Source ZIPs and JSON metadata. Not Built contains pending/failed sources; successful sources live under their primary output type.
▶
Processing / Active Workspaces
Temporary extracted build directories. Active workspaces are protected; anything not tied to a live build is stale.