wag-release-notes

Covers releases 2.5.0 to 2.5.3.

Features & improvements

  • Google Safe Browsing screening now sends only hashed URL prefixes to Google rather than the target URL itself.

Fixes

  • Safe Browsing screening now uses a compatible Google endpoint, restoring screening of configured target URLs.
  • Invalid, oversized or corrupt app-icon uploads now receive a clear failure reason.
  • More signing and other build failures now provide clear, safe guidance without exposing diagnostic details.

Known issues

N/A

Covers releases 2.3.0.

Features & improvements

  • Safe Browsing block alerts. When operator alerting is configured, a refused Safe Browsing build now sends the operator an email with the full target URL, threat type, submitter IP, and timestamp. Alerts are sent asynchronously and throttled, while every flagged build continues to receive its 403 refusal; without alerting configuration, the notification is silently skipped.

Fixes

N/A

Known issues

N/A

Covers releases 2.2.0.

Features & improvements

  • Optional Safe Browsing screening. When an operator configures a Google Safe Browsing API key, target URLs are checked and builds for flagged URLs are refused with a 403 response. Lookup screening discloses the target URL to Google; if the service is unavailable, misconfigured, or returns an invalid response, the build proceeds.

Fixes

N/A

Known issues

N/A

Covers releases 2.1.0 to 2.1.6.

Features & improvements

  • Managed configuration. Device management systems can now update selected installed-app settings, including the URL, appearance, orientation and relevant capabilities, without rebuilding the app.
  • Recognised signing problems now provide clear, safe guidance, such as identifying a wrong password, missing key alias or invalid keystore.
  • Studio now explains when a site's icon cannot be auto-filled, so you can add a compatible image in Branding.

Fixes

  • Studio safely discards invalid saved or imported configuration values instead of repeatedly crashing.
  • Site icon fetching no longer proxies SVG icons, preventing scripted SVG content from running on the Web App Generator origin.

Known issues

N/A

Covers releases 2.0.0.

Features & improvements

  • Allow plaintext HTTP. A new build-time control lets you explicitly permit an http:// target URL for its host and subdomains, and is retained when exporting or importing app configuration.

Fixes

  • Plaintext http:// target URLs are now rejected unless explicitly allowed, preventing them from being silently included in generated apps.

Known issues

N/A

Covers releases 1.7.0 to 1.7.1.

Features & improvements

  • Post-build feedback. The Studio success screen now links directly to in-app feedback, making it easy to report an issue, request a feature, or ask a question after a build.

Fixes

  • Photo upload capture. A page's take-photo control now opens the device camera and returns the photo to the page when the Camera capability is off. Enabling that capability retains the document picker behaviour because Android will not launch the camera app in that configuration.

Known issues

N/A

Covers releases 1.6.0 to 1.6.1.

Features & improvements

  • Clearer build handover. Build success screens now lead with what the update code is for and promote downloading the app configuration as the primary way to save it. The APK download is held behind a one-time prompt until the code has been copied, the configuration downloaded, or the warning acknowledged.

Fixes

  • The Studio APK download guard can no longer be bypassed by a second click or a failed clipboard copy, and a blocked copy now reports "Copy failed" rather than a misleading "Copied!".

Known issues

N/A

Covers releases 1.5.0 to 1.5.4.

Features & improvements

  • App-icon and keystore upload fields now show their maximum file sizes in both build interfaces.

Fixes

  • Oversized app-icon and keystore uploads are now rejected with a clear message instead of being silently truncated.

Known issues

N/A

Features & improvements

N/A

Fixes

  • Hardened the feedback endpoint against cross-site form posts.
  • Feedback delivery now reports delivery failures to the user instead of accepting a message that could not be sent.
  • Added coverage for feedback relay safety, sanitisation, rate limiting, and the anti-spam honeypot.

Known issues

N/A

Features & improvements

  • Added an in-product feedback widget to Studio and the classic form.
  • Studio includes a Feedback action in the header, with a compact fallback in the collapsed mobile menu.
  • Feedback is sent through the generator service, so it works from the public /webapp/ route without opening a separate contact page.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Added a header back button linking WAG back to the generator homepage.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Refreshed the default WAG app-gen brand mark across favicons, Apple touch icon and generated Android launcher icons.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Added GET /api/stats, a public total_apps counter scoped to the active WAG package prefix and cacheable for 60 seconds.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Added an inline Debug signing note below the signing options, making it clear Debug builds are for local testing only and cannot be deployed through Google Play.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Generated apps now show a more useful Android version name, combining the WAG builder version with the generated version code for easier support and upgrade comparison.

Fixes

N/A

Known issues

N/A

Features & improvements

N/A

Fixes

  • Generated APK versionCode values now use finer time granularity, avoiding collisions for builds submitted close together while keeping long-term Play Store headroom.

Known issues

  • Reproducible builds remain a separate consideration because versionCode is still generated from build time.

Features & improvements

  • The generator now states more clearly that app icons are not stored server-side and must be uploaded again for future rebuilds.

Fixes

N/A

Known issues

N/A

Features & improvements

  • The config import control now appears as a compact right-aligned chip, keeping the first-build form cleaner while still making rebuild workflows easy to access.

Fixes

N/A

Known issues

N/A

Features & improvements

  • The config import control was aligned with KAG's file-picker pattern for a more consistent generator experience.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Added web_app_config.json export and import so existing wrapper builds can be recreated without refilling the form.
  • Added a config download endpoint for commercial/API workflows.
  • Added config_json support on build submission, allowing imported configs to be used as defaults with explicit form fields still taking precedence.

Fixes

N/A

Known issues

  • Icons and keystores are intentionally not embedded in exported config files and must be supplied again when rebuilding.

Features & improvements

  • The build form now places Display mode and Orientation above the Options list, making the main layout choices easier to find before setting runtime behaviours.

Fixes

N/A

Known issues

N/A

Features & improvements

  • The default app icon was refreshed to the Bayton sparkle mark, replacing the generic Android placeholder when no custom icon is uploaded.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Added the Trust user CAs option. This supports enterprise networks using MDM-distributed root certificates, internal certificate authorities, or SSL inspection, while still allowing stricter system-store-only builds when required.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Source archives now include a signing.properties.template.
  • Release builds from downloaded source can be signed locally by filling in the template, regardless of how the original hosted build was signed.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Download filenames now use a shorter job-ID segment, keeping them traceable without being unnecessarily long.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Added build-failure alerting and service liveness monitoring for hosted deployments.
  • Download filenames now include traceable build details to make support and audit work easier.
  • Asset and API references were made relative for more flexible hosting behind path prefixes.

Fixes

  • Tidied several user-facing build-status messages.
  • Improved spacing on rebuild and duplicate-build callouts at small screen sizes.

Known issues

N/A

Features & improvements

  • Added fullscreen inset handling for devices with display cut-outs, camera holes, rounded corners, or unusual system-bar behaviour.
  • Added build provenance to generated APKs so support can identify which WAG version produced an artefact.
  • Reworked the generated package namespace to align with the wider Bayton generator family.

Fixes

  • Offline-page retry now works without relying on JavaScript.
  • User-agent overrides are truncated safely for multi-byte characters.
  • Cross-product update codes are rejected so KAG and WAG package identities cannot be mixed.

Known issues

N/A

New features

  • Initial public release of WEB APP GENERATOR. The service can wrap a URL in a signed Android APK or AAB using a native WebView, with display-mode options, runtime capability toggles, signing choices, update codes, API support, and downloadable source archives.

Fixes

N/A

Known issues

N/A

What are notes?

These are short-form posts for small updates and quick thoughts. They are automatically published to social channels, and have their own RSS feed, too.

mail Reply by email | edit_note Edit this page | code_blocks Code
Ask MIKA
MIKA Mobile Intelligence & Knowledge Assistant