Android 17 Without the Last-Minute Scramble

One of the bugs in our Android 17 preparation was a version number. The platform was 37.2. One builder path removed the punctuation and read it as 372.

That number sailed through minimum-version checks. A different path tried to parse the suffix as an integer and failed outright. Neither had anything to do with the application a customer was trying to build.

This is the work we want to do before a target-SDK deadline arrives. The API 37 changes check the new platform and fix its path through the builder. The location button then exercises a new permission flow in a generated application. Along the way, PEM parsing and task removal take two more recurring pieces of security code out of individual apps.

Make the new platform break our build first

We kept the normal SDK floor at 36 while adding these API 37 checks. That lets us work through migration failures before changing the default for customer builds.

The source check compiles identical sources against two platform jars and compares errors. Optional packages with unresolved dependencies can fail identically in both runs; the useful signal is an error introduced only by the newer platform.

A second android.jar on the classpath would defeat that check by supplying a removed symbol from the old stub. The script removes those duplicate platform jars. A fault-injection probe using removed fingerprint APIs proved that the comparison detects the regression it was designed to catch.

The platform name is no longer an integer

The installed API 37 packages use names such as android-37.0, android-37.1, and android-37.2. Treating the whole suffix as an integer failed outright on one builder path. Removing punctuation before parsing was worse: 37.2 became 372, which silently passed every ordinary minimum-version check.

The builder now extracts the major API level correctly, updates build-tools handling, and uses the SDK manager associated with the SDK root actually being built. The generated-project check then assembles against the new platform, covering failures a source-only check cannot see.

This continues the platform-watch work from last week. The goal is to turn a future platform requirement into a failing check while there is still time to fix the producer.

One-time location belongs behind a deliberate action

Android 17 introduces a system-rendered location button for transactional precise-location access. Google’s policy page, checked September 10, lists January 27, 2027, for compliance and describes the Android 17+ enforcement timing as subject to further updates. The dates come from Google Play’s location policy; the general target-SDK schedule is a separate requirement.

The Codename One component presents the platform control where supported and an ordinary button elsewhere:

import com.codename1.location.LocationButton;

LocationButton location = new LocationButton(
        LocationButton.TEXT_USE_PRECISE_LOCATION);
location.addLocationSharedListener(fix -> {
    if (fix != null) {
        searchNearby(fix.getLatitude(), fix.getLongitude());
    }
});
form.add(location);

searchNearby is application code. A null result is a normal outcome when permission is declined or no location is delivered. The component exposes isSystemRendered() so the application can inspect which path is active.

Android’s location button ties the precise-location request to a visible user action and a session-scoped grant. For a task that works with coarse location, keep the request coarse.

Use the platform protocol without forcing an AndroidX upgrade

The earlier implementation depended on an AndroidX library whose metadata required compile SDK 37 and Android Gradle Plugin 9.1.0. That would have made a new button force a toolchain migration for every generated application using it.

The platform already exposes the session API beneath that wrapper. The merged implementation reaches it through reflection and implements the callback interface through a Java proxy. The system draws its control into a surface hosted inside the Codename One component.

The rest of the Codename One screen keeps its custom rendering; the OS owns this consent surface.

Permission injection and fallback still need attention

The generated manifest must include USE_LOCATION_BUTTON. The repository builder adds it when the application references LocationButton. The separate BuildDaemon mirror was still pending with this change, so the cloud builder needs that update too.

The implementation also avoids automatically restricting all precise-location permission to button-only access. An application may have a legitimate continuous-location feature as well. That decision requires reviewing the application’s actual location use and current platform guidance, rather than inferring policy from the presence of one class.

If a platform session fails, the component falls back to the ordinary button. That preserves a usable control, but an app targeting the new transactional-location requirements should test that the system path really remains active. Check isSystemRendered() while testing that flow.

The button on Android 17

We ran the generated app on an Android 17 emulator with compile SDK 37.2 and target SDK 37. The system button rendered, a human tap opened the platform consent sheet, and approval produced a location with the session-scoped permission flags. The same APK on API 36 used the ordinary button and permission flow.

The regular screenshot CI leg is still on API 36. Expanding that coverage to API 37 is part of the remaining migration work.

The key file is right there. Why are we converting it by hand?

Loading a key often started with a small conversion task: remove the PEM armor, decode Base64, and work out which DER container was inside. That is a poor place for every application to maintain its own slightly different parser.

PEM parsing puts that work into the security API.

PublicKey.rsa() and PrivateKey.rsa() take DER bytes in the expected key container. PEM adds textual armor and Base64 encoding. Passing the whole armored file to a Base64 decoder does not reliably strip the labels for you, and stripping them still leaves the question of which container is inside.

The new entry points accept text or raw file bytes and read the algorithm identifier from the key:

import com.codename1.security.PublicKey;
import com.codename1.security.PrivateKey;
import com.codename1.io.Util;

PublicKey publicKey = PublicKey.fromPem(
        Util.readInputStream(publicStream));
PrivateKey privateKey = PrivateKey.fromPem(
        Util.readInputStream(privateStream));

The streams in this excerpt come from the application’s existing key-loading flow. The application chooses the key source and its trust policy; the parser handles the file format.

Unarmored Base64 is also accepted for a supported key container. CRLF, blank lines, and text around the PEM block are tolerated.

Validate the container before the platform sees it

A truncated DER element can contain enough bytes to name an algorithm and still be unusable. The parser checks the complete element rather than handing a partially decoded key to the platform and waiting for a less useful error.

We cross-checked the generated keys against JCE and OpenSSL conversions. A 294-case truncation test checked that damaged input fails with a useful error instead of ArrayIndexOutOfBoundsException. EC byte conversion was checked separately because that Java 8 environment lacked SunEC.

The result is a key object ready for the application’s verification flow. Certificate validation and trust decisions stay with that flow.

End the task when the session is finished

PR #5746 adds an explicit way to remove an Android task from recents when exiting.

Android’s process and its task have separate lifecycles. The old exit path killed the process but could leave the task available in the switcher.

The new request is explicit:

import com.codename1.ui.CN;

// Call after the application's sign-out cleanup has completed.
CN.exitAndClearTask();

On Android, the port calls Activity.finishAndRemoveTask() on the UI thread and then follows the existing process-exit behavior. If no Activity exists, or on an Android version before API 21, it falls back to ordinary exit. Other ports retain their existing exit behavior. CN.isExitAndClearTaskSupported() allows the UI to distinguish support.

The setOnExit callback still runs. If sign-out requires asynchronous server work, finish that work before invoking the exit rather than assuming a callback can keep the process alive until a request completes.

What task removal protects, and what it leaves to the app

Removing the task prevents that task from remaining as an ordinary entry in the task switcher. It does not revoke a token, erase local files, clear a server session, or stop someone launching the app again from its icon. It also does not substitute for protecting sensitive screenshots while the task is active.

For an app using continuity, clearing and disabling saved-state restoration is another explicit part of logout:

Continuity.clear();
Continuity.disable();
// Complete account/session cleanup, then request the exit.
CN.exitAndClearTask();

Complete credential and account-data cleanup before process termination, including any asynchronous sign-out requests.

On an API 36 emulator, removing the task before killing the process removed it in all 29 executed trials. Killing the process alone left the task in recents.

Make the common security operations harder to get wrong

The location button, PEM parser, and task-clearing exit each replace a piece of platform or format code that app teams should not have to reconstruct. Application code can concentrate on whom to trust, which location it needs, and when the account has finished signing out.

That work closes a week in which we also reduced garbage, made caches reclaimable, improved maps and boxed values, and removed unnecessary native waits and JavaScript suspension. Continuity and native drag and drop give users more ways to move their work; integrated Javadoc makes the contracts easier to find. The release overview links the full series.

We are strengthening Codename One’s advantage by maintaining the Java API, runtime, and platform integration together. That lets a reference-safety fix, a stricter key parser, or an OS-owned consent control reach applications through the framework. Customers should spend less time repairing platform glue and more time on the authorization and data rules specific to their product.

API 37 preparation continues before we require a migration, and more performance work is already underway. We will keep reporting the measurements that improve and the cases that still need attention. The version-number bug was a small reminder of how much work can hide behind a platform upgrade. Finding it now keeps it out of a customer’s release scramble.

Discussion

Does your sign-out flow test saved-state restoration and relaunch from recents as well as launch from the app icon?