We Stopped Waiting for Platform Changes to Find Us
For years, our warning system for Apple and Google changes was a developer whose build failed first. The community gave us excellent reports, but the sequence was backwards. A platform owner announced a deadline, time passed, an application hit the change, and only then did we trace it into the builder. What is Codename One? Codename One is an open-source framework for building native iOS,…
Codename One, an open-source framework for building native apps, recently introduced a daily scheduled Codex task to address platform changes. Traditionally, the community would wait for a developer's build to fail after a platform owner announced a deadline, but this new approach reverses the sequence. By checking official notices against Codename One, the task identified two changes: Android 16 back handling and a permission-safe Contact Picker.
The Android builder still compiles against an older SDK surface, so the fix uses reflection and a proxy instead of linking the newer class directly. The Contact Picker, which returns a selected snapshot instead of granting permanent permission, is now available on Android 17, Android versions with permission-free single-contact fallbacks, and iOS.
This change moves security work into the normal release cycle and helps developers choose a narrower API instead of making deadline patches that widen access.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
