The Studio build-success screen now links directly to feedback, making it easier to report a problem, ask a question or suggest an improvement after a build.
Recognised signing failures now provide targeted, safe guidance, while unrecognised failures keep the general build-failure message.
Fixes
Managed configuration changes now reconcile autostart immediately, and a typed app or folder policy no longer leaves an unexplained blank launcher: when no configured app is installed and launchable, the launcher explains why (a configuration error for malformed policy, or a waiting message while valid apps arrive), and an intentional empty managed collection preserves the existing baseline. Launcher availability feedback also stays current as managed apps are added, removed, replaced or updated.
Studio now safely discards invalid values in imported or saved configurations instead of repeatedly crashing, and folders continue to open in the preview after their colour is changed.
Wallpaper handling is more reliable: cold launches avoid duplicate bitmap decoding, and a URL wallpaper now replaces its fallback after it finishes loading.
Leading and trailing spaces are now trimmed from self-signing key aliases, preventing avoidable build failures late in the build.
Known issues
N/A
Further support or feature requests
Are you in need of further help, or would you like to raise a feature request? You can: