cag-release-notes

Covers releases 1.5.0 to 1.5.2.

Features & improvements

N/A

Fixes

  • Clearer build-failure guidance. More signing, resource, memory, disk, dependency and SDK licence failures, plus unsupported, oversized, corrupt or truncated app-icon uploads, now receive fixed, user-safe guidance instead of a generic build failure.

Known issues

N/A

Covers releases 1.4.0 to 1.4.7.

Features & improvements

  • Clear managed-configuration status. The EMM now receives the specific invalid field when a push is rejected and a recovery signal when a later push is accepted. These reports contain no contact data or source URLs.

Fixes

  • Safer managed configuration. Invalid, partial or wrongly typed managed-configuration pushes retain the last known good configuration. If none exists, the app skips the sync rather than applying defaults. An explicit empty sources list remains a valid instruction to clear the current directory only when delete-missing is enabled.
  • Actionable build-failure guidance. Recognised signing failures now show targeted, fixed guidance instead of a generic build failure. Unrecognised failures keep the generic message.
  • More reliable managed contact updates. Removing, clearing or reconfiguring a source, or renaming its account, no longer leaves its contacts empty when it is added again or changed.
  • Validated configuration values. Invalid network timeouts and sync intervals are rejected before they can create an unusable app, and invalid imported or saved Studio values no longer cause a crash loop.

Known issues

N/A

Covers releases 1.3.0 to 1.3.1.

Features & improvements

  • Build-screen feedback link. The Studio build success screen now links directly to the feedback form for reporting bugs, requesting features or asking questions.

Fixes

  • Reliable self-signing aliases. Leading and trailing whitespace is removed from self-signing key aliases so valid keystore aliases do not fail during the build. Passwords are unchanged because their whitespace can be intentional.

Known issues

N/A

Covers releases 1.2.0 to 1.2.1.

Features & improvements

  • Clearer update-code protection. The build success screen explains that the update code preserves an app's package identity, makes downloading the app configuration the primary save action, and prevents APK downloads until the code has been saved, copied successfully or explicitly acknowledged.

Fixes

N/A

Known issues

N/A

Covers releases 1.1.0 to 1.1.5.

Features & improvements

  • Upload fields now state their maximum size, so the limit is visible before a build is rejected.

Fixes

  • Prompt managed-configuration updates. When sync_on_config_change is enabled and the app is running, a managed-configuration push now re-syncs promptly and refreshes the open contact list, branding and status in place, where previously the change was not delivered. Wi-Fi-only sync settings continue to apply.
  • Safer uploads. Icon, keystore and source-file uploads over their size limits are rejected rather than being accepted as truncated files that could produce a corrupt app.
  • Security settings fail safely. Invalid rate-limit settings now stop startup rather than silently disabling rate limiting, and the alerting token is not sent to non-HTTPS servers, except permitted loopback HTTP addresses.

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 /contacts/ route without opening a separate contact page.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Added branding_accent as a flat managed-configuration key for generated CAG apps.
  • Deployed apps can now be re-tinted by EMM managed configuration without a rebuild.
  • Runtime accent resolution now uses the effective managed configuration first, then falls back to the baked build accent.
  • Validated the key through Android's managed-configuration path on a generated app.

Fixes

  • Corrected CAG documentation to describe the accent as EMM-configurable.

Known issues

N/A

Features & improvements

  • Added a Studio header home button that returns to the gen.bayton.org generators hub.
  • On narrow screens, the home action appears as a full-width item in the collapsed header menu.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Studio now confirms before importing a config over an in-progress build.
  • The welcome screen remains exempt because no operator-entered configuration exists there yet.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Studio's live preview now reflects the selected theme mode.
  • Light and Dark render explicitly; Auto follows the preview system day/night setting, matching the generated app.

Fixes

N/A

Known issues

N/A

Features & improvements

  • Renamed individual managed-configuration override keys from dotted names to underscore names for better EMM console compatibility.
  • The whole config_json shape is unchanged; only flat single-key managed-configuration overrides are affected.

Fixes

N/A

Known issues

  • This is a breaking change for EMMs already pushing dotted keys such as branding.theme_mode. Switch to the underscored equivalent, such as branding_theme_mode.

Features & improvements

  • Added downloadable CSV and JSON starter files for contact sources.
  • Linked starter files from the classic form and Studio docs.
  • Clarified that VCF is the standard vCard format and should usually be exported from an existing contacts system rather than hand-authored.

Fixes

N/A

Known issues

N/A

Features & improvements

N/A

Fixes

  • Fixed release-build crashes caused by R8 stripping WorkManager/Room classes needed by the generated app's sync scheduler.
  • Verified minified release APKs launch through WorkManager initialisation to the normal first-run flow.

Known issues

N/A

Features & improvements

  • Initial stable CONTACTS APP GENERATOR release.
  • Generates signed Android Managed Contacts apps from VCF, CSV, or JSON sources.
  • Supports built-in contact files, URL-backed sources, managed configuration, Studio and classic build surfaces, signing modes, source export, config export, and update-code reuse.
  • Raises embedded source-file support to 32 MiB to match the generated app's runtime source ceiling.

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