Titanium SDK 9.3+ AndroidX Compatibility: Should the SDK Enforce AndroidX‑Only Mode?
0 reputation · 06 Nov 2024, 10:28 UTC
Titanium SDK 9.3+ AndroidX Compatibility
The 9.2.0 release resolved a documented memory leak in Ti.UI.WebView on Android by cleaning up native Chromium resources during the view’s destroy lifecycle. While this fix stabilizes heap usage, a new configuration boundary emerged with SDK 9.3.0: the build process defaults to AndroidX libraries, yet the SDK still ships legacy android.support shims. Developers must opt‑in via the useAndroidX flag in tiapp.xml to avoid duplicate class errors, leaving the decision to manage potential runtime crashes when both sets coexist.
Given this dual‑library state, the SDK team faces an unresolved policy question: should future major releases automatically enforce an AndroidX‑only mode and strip the support‑lib shims, or continue to leave the configuration to the developer? The choice impacts backward compatibility, build size, and runtime stability.
Key unresolved questions:
- Will automatically enabling AndroidX‑only mode in the next major SDK eliminate duplicate class issues without breaking existing apps?
- What migration path should developers follow to transition legacy support libraries to AndroidX safely?
- How will the removal of support‑lib shims affect the debugging and profiling of
Ti.UI.WebViewmemory usage in current projects?
titaniumsdk