Android 17 behaviour changes for targetSdk 37 (CtrlProxy audit)¶
CtrlProxy reads targetSdk = 37, compileSdk = 37 and buildTools = 37.0.0 from
android/gradle/libs.versions.toml. The Robolectric maximum stays 35, with the CtrlProxy SDK 24
and Playground SDK 30 test pins.
Facts the targetSdk 37 behaviour changes depend on:
- Local network. The only listener binds loopback:
embeddedServer(CIO, host = "127.0.0.1", ...)inWebSocketServer.kt, reached from the host throughadb forward. The prototype device client makes outbound LAN calls (for example to 10.0.2.2), so CtrlProxy declaresACCESS_LOCAL_NETWORK. - Cross-profile reads use no socket:
SdkCapabilitiesDiscoveryaddresses another user’s provider throughcontent://<userId>@<authority>(binder, gated onINTERACT_ACROSS_USERS). - No TLS of its own. CtrlProxy main has no
HttpURLConnection,HttpClient,SSLContext,TrustManagerorDownloadManager; the Ktor client istestImplementationonly.MANAGE_CA_CERTIFICATESserves target apps’ interception, not CtrlProxy traffic. - No background launches through
IntentSenderand no orientation, resizability or aspect-ratio locks in the manifest (includingSavedPrototypeActivity, whoseconfigChangeshandles orientation and screen-size changes without locking them). - IME.
CtrlProxyIme.ktcommits withcommitTextand uses noTextAttribute;TextAttribute.Builder.setTextSuggestionSelected()is API 37 only and would need anSDK_INTguard.