March 25, 2026

API Changes

Bug Fixes

  • Moves libraries to use Java 11 target. This means produced bytecode will be Java 11 (class file version 55) and might require desugaring to use the library If4c2a b/457821470
  • SearchFeatures and RankingFeatures. I54b7d b/387291182
  • Use new delete propagation flag If21ae b/384947619
  • Adds more detailed internal logging I10604 b/448872333
  • Adds back allowoptimization to proguard keep rule for AppSarchDocumentClassMap I0bd88 b/440484133
  • Fixes a bug in optimized builds where references to AppSearch document classes could be replaced by unrelated classes due to horizontal class merging I93f20 b/440484133
  • Add ISOLATED_STORAGE feature Ifb963

API Changes

  • Changed Config.augmentedObjectCategories from a List to a Set. I25a64 b/487376359
  • The types androidx.xr.arcore.Eye and androidx.xr.arcore.Hand. I42438 b/449032900
  • Added Session.create overload to allow passing an Android Context for resource-scoping. I7d3fe b/415805990 b/477386334
  • Changes FakeRuntimeAnchor.ANCHOR_RESOURCE_LIMIT to FakeRuntimeAnchor.anchorResourceLimit. I90841 b/431992235
  • Making TiltGesture API experimental as it may be changed or removed in the future. To use this api, opt in to @ExperimentalGesturesApi Ic9858
  • Added ability to set categories for AugmentedObject tracking in the Config I1f6e4 b/480220930

Bug Fixes

  • Fixed Chrome's build by updating META-INF/services/ file with actual location of PerceptionRuntimeFactory. I7a801 b/481288291

Bug Fixes

  • Updated ArtMetric to account for top-level packages, especially important when using AGP/R8 9.1+, or -repackageclasses global option. Previously, ArtMetric would fail to detect these classloads in its artClassLoad... measurements. If8a35 b/487402058

New Features - Added a new instrumentation argument androidx.benchmark.requireLockedClocks that allows enabling a check for whether the CPU clocks are locked for rooted devices. Id82e8 b/468039042

New Features

  • Multiple Fallback Options Support Ib078e b/349218025
  • Starting with Android 36.1 (Baklava), biometric prompt now supports up to four custom fallback options instead of a single negative button. Developers can provide multiple custom fallback options with associated icons (on supported Android versions) via AuthenticationRequest.Biometric.Fallback. Clicks on these options are now delivered via AuthenticationResult.CustomFallbackSelected instead of an error code.

API Changes

  • Remove JvmSynthetic from AuthenticationRequest. Ia2dcb b/434257610
  • Add KeyAgreement support to BiometricPrompt.CryptoObject. I73029 b/400115331
  • Update registerForAuthenticationResult() to use ComponentActivity instead FragmentActivity for broader compatibility. Id5db6 b/349213716

Bug Fixes

  • Fixed an issue where the fingerprint icon would disappear during device rotation. I366f2
  • Moved fingerprint dialog destruction to onDestroy(). I619b0
  • Updated the compileSdk to version 36.1 to support new Baklava platform features. I9da03

Important changes since 1.5.0:

1. Migrated to a High-Performance, Unified Camera Stack

  • CameraX now uses CameraPipe—the same modern, high-performance stack powering the Pixel camera. This transition streamlines architectural efficiency and provides a scalable foundation for bringing advanced computational photography features to the developer ecosystem.

2. Media3 Muxer Integration

  • CameraX now integrates the Media3 Muxer by default within the VideoCapture API. This migration provides several benefits:
    • Enhanced Performance: More efficient video processing and muxing.
    • Crash Resilience: Improved protection against video file corruption, ensuring that data is preserved even if the application crashes during recording.

3. Feature Group improvement

4. Stabilized SessionConfig API

Bug Fixes

  • Fixed a crash that occurs on certain Android 17 (API 37) devices or higher. When these devices expose new dynamic range profiles (e.g., STANDARD_SMPTE_2094_50(ID 8192)) that were unknown to CameraX version 1.5.1 and earlier, the library previously failed to handle these IDs appropriately, resulting in a NullPointerException or IllegalArgumentException during ProcessCameraProvider.bindToLifecycle(). This fix allows CameraX to gracefully ignore unrecognized dynamic range profiles, preventing the crash and maintaining forward compatibility. Please update your CameraX dependency to version 1.5.2 or 1.6.0 (or higher) to avoid this issue on devices exposing these new profiles. For more details, see issue 519796838. Ibd7b5
  • The feature group API now provides consistent results when PREVIEW_STABILIZATION is used with VideoCapture. This corrects a bug that caused inconsistent results when a Preview use case was not also active. Ifed82 b/449913903
  • Fixed an issue where unsupported preferred features were incorrectly made available. Features are now correctly filtered when their required use cases are not met. I38db8 b/449532342
  • Fixed glitchy video result on Samsung Galaxy S6. I612d9 b/235127608
  • Fixed an issue where CameraInfo#isFeatureGroupSupported could incorrectly return true for PREVIEW_STABILIZATION if the SessionConfig in the query was already configured with other features. I2c355c b/437816469
  • Excluded problematic YUV format output sizes from Samsung Z Fold 4 device. The received images have distortion issue when using those output sizes. I776bf b/460322307
  • Fixed a device-specific issue on Samsung A53 where image capture with torch enabled would fail sometimes if VideoCapture use case is bound. I0f183 b/458197367
  • Fixes an issue on some devices where using the flash with the ultra-wide camera may result in underexposed images. Ib7530 b/444590340
  • Updated the ExifInterface dependency to include a fix for parsing JPEGs with 0xFF padding, which resolves image capture failures on devices where the JPEG encoder adds fill bytes before markers. I0eb49

Important changes since 1.5.0:

  • Exposed the default viewfinder ImplementationMode via the new ViewfinderDefaults.implementationMode public API. This is now used as the default for both ViewfinderView and the Viewfinder composable. Ic3f52

Bug Fixes

  • SeekableTransitionState now properly handles off-thread state changes. Previously, if the state was modified off the UI thread using Snapshot.withMutableSnapshot(), the transition incorrectly tried to handle the update off of the UI thread.0aba38
  • Validate duration in InfiniteRepeatableSpec to prevent 0-duration cycles 151b6d
  • Respect visibilityThreshold in custom AnimationSpec for animateFloatAsState 3a1cdc
  • Fixed the corner case interruption handling when a child exit animation finishes while the parent transition is still running in AnimatedContent. ad9b4f

API Changes

  • Added flag isReverseLayoutNestedScrollConnectionInPagerFixEnabled to control the rollout of this fix. I07404 b/399800244
  • Introduce isSkipItemPlacementAnimationFixEnabled to control the rollout of this feature. Id665d b/455884472 b/352584409 b/410487464 b/372509998
  • Added MinMax(min: Dp, max: Fr) to GridTrackSize. This allows developers to explicitly define the minimum bounds of a flexible track. Using MinMax(0.dp, 1.fr) successfully bypasses intrinsic measurement queries, making it safe to place SubcomposeLayout components like LazyColumn and LazyRow inside flexible grid tracks without crashing. Ieb8c2 b/483822148

Bug Fixes

  • Fixed a bug in FlexBox where items shrank incorrectly when hitting their minimum intrinsic sizes. Items now correctly share unconsumed shrink space to siblings. Additionally, FlexBox will no longer artificially clamp items on main axis; if items cannot shrink enough to fit the container, they will now visually overflow the main axis. Use Modifier.clipToBounds() if clipping is desired. Ief751 b/480797591
  • Prevent keep around from accessing illegal indices. I19121 b/485626636
  • Fixed an issue in Grid where gaps between implicitly created rows or columns were omitted from the container's total size calculation, which resulted in clipped content. Ib9df8 b/480372415
  • Clipboard and ClipboardManager now request the system service on the first method call If0016 b/487947860
  • Fixed an issue in Row with Arrangement.spacedBy in RTL where overflowing items would result in incorrect layout and spacing. I44e53 b/476006478

New Features

  • Promote Typography constructors and attrs, Added a Typography constructor that accepts a default FontFamily to be applied to all TextStyles in the scale. I3f6f1 b/236358112
  • Promote experimental APIs for sliders to stable. I5efb3 b/304811984

API Changes

  • isAnchoredDraggableComponentsAnchorRecoveryEnabled feature flag introduced for draggable components experiencing ambiguous target errors. Components include ModalBottomSheet, BottomSheetScaffold, SwipeToDismissBox and WideNavigationRail I5b0e5 b/487941042 b/478210200 b/477038695
  • Added DropdownMenuItemTrailingLabel default function and pointer optimized UI paddings for segmented menus I28977 b/485937388
  • Added paddings for dialogs for when ComposeMaterial3Flags.isPrecisionPointerComponentSizingEnabled is true, and added AlertDialogDefaults.IconSize for the icon. Ib9652 b/485932651
  • Optimized BasicTextField's internal min size calculations. These are controlled by ComposeFoundationFlags#isBasicTextFieldMinSizeOptimizationEnabled, should you need to disable them. I70ade
  • Updated parameter order in SearchBarDefaults.InputField to maintain source code compatibility. I20e3b b/486964336
  • Remove deprecated FilterChip and AssistChip api that have a horizontalSpacing parameter Iec623 b/483762893
  • The isAtTop parameter in TopAppBarDefaults.pinnedScrollBehavior and TopAppBarDefaults.enterAlwaysScrollBehavior has been renamed to isAtStart If7323 b/405129274

Bug Fixes

  • BottomSheet components now respect MaterialTheme.motionScheme during nested scroll and drag gestures. I5fe22 b/452071842 b/384959324
  • Fixed icon-label padding being applied when the item has a selectedLeadingIcon that is not currently displayed Iba820

Bug Fixes

  • Fixes an issue in WASM where identity hash codes would always return 0 I9d70c
  • Fixes an issue where a parent derived state might fail to invalidate correctly when the dependencies of a nested derived state change Ia7981 b/481750019
  • Fixes an issue in the LinkTable that can cause invalid writes after disposing a composition. I5c97a
  • Fixes an issue in the LinkTable that can cause invalid writes when the table resizes during a copy operation Ie7edf
  • Fixes an issue in the LinkTable that incorrectly updates the stored value of a node I58a4a
  • The LinkTable now initializes to a smaller capacity, which prevents OOM errors when creating many subcompositions on devices with smaller heap sizes I112b9

API Changes

  • Rename PreviewWrapper API for consistency I62659 b/490085948
  • ComposeViewContext allows a ComposeView to compose without being attached to the view hierarchy. Use AbstractComposeView.createComposition(composeViewContext) to start composing without the ComposeView being attached. I46e6f
  • Added delayMillis to trackpad test APIs for panEnd and scaleEnd If80fe

Bug Fixes

  • Clipboard and ClipboardManager now request the system service on the first method call If0016 b/487947860
  • Focus will be restored correctly inside lazy containers where focus nodes and groups are being reused I18d36 b/481564275
  • Popup with clippingEnabled = false now correctly uses the full window bounds to display edge-to-edge I206408 b/327017902

Bug Fixes

  • Fixed an issue on older Android versions where incoming or upgraded video calls would sometimes incorrectly route audio to the earpiece. The library now enforces a switch to the speaker if this misrouting is detected. I0fc797 I29fd22
  • Removed A2DP Bluetooth devices from the list of available endpoints shown in the pre-call screen, as these devices are not supported for voice communication by the Android platform Telecom framework. This aligns the available devices with platform behavior. I98b729
  • Skipped running call extensions logic for managed calls to prevent potential crashes or unexpected behavior. I177905

New Features

  • Define the operations for Wear Widgets profile inline.

API Changes

  • We have renamed CONTAINER_TYPE_FULLSCREEN to CONTAINER_TYPE_TILE_COMPAT to better differentiate fullscreen compatibility widget. This includes reverting of mapping previously FULLSCREEN type to LARGE in Widget params.

API Changes

  • Adjusted the default values for primary, positive, negative, and surface. Added a new color axis called "background". I6bb6c b/481671956
  • Added a ComponentSpacingValues subsystem in GlimmerTheme that provides values for use across components for paddings and other spacing elements. Existing PascalCase spacing and padding constants in component Defaults objects (e.g., ContentPadding, ItemSpacing) have been renamed to camelCase and converted to Composable properties. I96e30 b/491166461
  • Move onClick to the last position in parameter list to be used as trailing lambda. Don't consume IndirectPointerEvent(s) if no applicable lambda is provided I9343e b/486965466
  • Renamed Depth and related entities to DepthEffect. The layer properties of DepthEffect are made public. Ie26d2 b/485632564

New Features

  • Introduce new fields to ExerciseSessionRecord and ExerciseSegment to support richer exercise tracking I3c176

API Changes

  • Add HealthConnectClient#getChanges(changeLogsToken, pageSize) to set a soft limit for the number of change logs returned I6837d
  • Enable support for activity intensity for Health Connect APK 8c7923c
  • Defer record validation checks to platform on Android U+ 7682d18

Bug Fixes

  • Fix aggregation for activity intensity and mindfulness 0b312833

New Features

  • Add message ports API to provide symmetric, flexible, and low-overhead communication with JavaScript isolates. This allows strings and ArrayBuffers to be sent and received without embedding them inside evaluations or named data blobs. I04bc0 b/490128971

API Changes

  • Add the SpatialGltfModel API and the SpatialGltfModelAnimation APIs to render glTFs and control animations. Changed SpatialGltfModelState to be AutoCloseable, it will now need to be closed to free its resources. I11fde b/466065486 b/481379924. However, the SpatialGltfModel API is marked as restricted for this release pending additional testing. Ibf003 b/466090694
  • Added a deprecated empty overload for SubspaceModifier.rotate. Idceb6
  • Renamed SpatialSmoothFeatheringEffect function to spatialSmoothFeatheringEffect and moved it to a draw module. Updated SpatialExternalSurface default feathering value to null, which mimics the old ZeroFeatheringEffect functionality. I5fdaa b/460426800
  • Removed onPointSourceParamsAvailable. A different audio spatialization API will be available in the near future. I86507 b/458513439
  • Added RTL behavior for offset subspace modifiers. Also added absoluteOffset to ignore layout direction. I30e4b b/474409165

API Changes

  • Removed unscaledGravityAlignedActivitySpace flag from Session.create. ActivitySpace is always unscaled and gravity-aligned now. If6f11 b/458173423
  • Removed deprecated setMaterialOverride and clearMaterialOverride functions from GltfModelEntity which are now called on the individual GltfModelNode. I2e5d2
  • Added transformPixelCoordinatesToLocalPosition and transformNormalizedCoordinatesToLocalPosition to PanelEntity and removed equivalent experimental methods that used to return poses instead of Vector3 positions. Ib6960 b/460123106 b/458333591
  • Added GltfAnimation APIs for controlling glTF animations in SceneCore. I2c172 b/466065486 b/465819070 b/465818617
  • Renamed ScenePose.activitySpacePose to ScenePose.poseInActivitySpace I8f175 b/427822261
  • Added Scenecore Projected Runtime Implementation I9c4ab b/476440158
  • When resizing the main panel entity, it may reposition itself to the ActivitySpace origin. There is no workaround other than manually or programmatically repositioning the panel back to its original location. This bug will be fixed in a future release. b/489427007.
  • In some cases, the affordance for MovableComponent may not appear for SurfaceEntity and other non-Panel entity types. Explicitly setting MovableComponent.size will cause the affordance to appear. This bug will be fixed in a future release b/490983469.

API Changes

  • Make parentKey an optional parameter in ViewModelStoreProvider constructors, defaulting to null, and move it after parentStore or parentOwner. This simplifies instantiation when a shared scope key is not needed. I66b67
  • ViewModelStoreNavEntryDecorator now accepts a ViewModelStoreOwner instead of a ViewModelStore. This allows Navigation3 to propagate the parent's default CreationExtras and ViewModelProvider.Factory to nested ViewModels, ensuring support for application-level dependencies. Ia6018 b/434651920
  • Isolate ViewModelStoreProvider state using a unique key. This prevents sibling providers from unintentionally clearing each other's ViewModels during disposal. I59c0b b/434651920
  • Add ViewModelProvider.get<VM>(key: String) extension function. This enables developers to more cleanly retrieve ViewModels using a custom key with Kotlin reified type parameters, removing the need to explicitly pass the class type. Ic1f59
  • Add defaultArgs support to ViewModelStoreProvider to allow initializing ViewModels with default SavedState values. I1e933 b/434651920 b/165642391
  • Deprecate removeViewModelStoreOnPop and the associated ViewModelStoreNavEntryDecoratorDefaults. This API was a workaround for configuration changes, which are now handled internally. All decorator state, including ViewModels, must now be cleared at the same time on pop. To keep decorator state around outside of when that back stack is passed to a NavDisplay, use the rememberDecoratedNavEntries API. I852d9

Bug Fixes

  • Add toString() to CreationExtras.Key to display the class name. I5de52

API Changes

  • Changed Orbiter to use either an OrbiterAnchorPoint + VolumeOffset or an OrbiterPoseProvider instead of position, offset, offsetType, alignment, and elevation. Also removed the shouldRenderInNonSpatial parameter. If the developer does not want the orbiter to render in non-spatial they should wrap the orbiter in an if statement and check the SpatialCapabilities. I9fbb3 b/462428503

Bug Fixes

  • NavDisplay now ensures that entries that are displayed underneath overlays have their Lifecycle capped at STARTED. This ensures APIs like dropUnlessResumed continue to work when using dialogs. If209f b/483966071
  • Fixed an issue in NavDisplay where navigating back and forth between the same screens and interrupting the animations between the two could cause the z-order of the screens to be incorrect. I4d491 b/459419800

New Features

  • EditablePdfViewerFragment now supports rendering and erasing highlight annotations added from other apps. Ic46e4

API Changes

New Features

  • Implement non-linear font scaling 73b23c0
  • Make layouts aware of LayoutDirection 81f984b

API Changes

New Features

  • FTS5 Support: Added FTS5 support to Room via the @Fts5 annotation. This includes new constants for FTS5 tokenizers (TOKENIZER_ASCII and TOKENIZER_TRIGRAM) and an enum for the 'detail' FTS option (FULL, COLUMN, and NONE). I90934 b/146824830
  • Room Paging Targets: Added js, wasmJs, tvOS, and watchOS targets to room3-paging. Icffd3 b/432783733

API Changes

  • Multi-platform clearAllTables(): Commonized clearAllTables(), making it available across all platforms. It has also been converted into a suspend function. I434ae b/322846465
  • Destructive Migration: Added a default parameter value to dropAllTables in the fallbackToDestructiveMigration APIs. Ica88b b/438041176
  • Experimental API Changes:

    1. Moved @ExperimentalRoomApi to room-common to allow annotation-based APIs to be marked as experimental.

    2. Added an experimental RoomWarning to suppress the requirement for @ConstructedBy in a Room database declaration. In this case, DatabaseConstructor will not be generated, and a factory implementation must be provided via DatabaseBuilder. If5443

Bug Fixes

  • Paging Source: Updated PagingSourceDaoReturnTypeConverter to correctly indicate that its convert function is intended for READ queries. I3b067 b/139872302

API Changes

  • Updated the client-side SecurityPatchState to support the new secure session model when communicating with update providers. This architectural change fortifies the client against IPC race conditions, preventing crashes and connection errors that could occur during coroutine timeouts or unexpected service disconnections. I2cf65

Bug Fixes

  • Updated the client-side discovery logic to enforce a stricter security boundary when identifying trusted update providers. SecurityPatchState now explicitly verifies that hosts hold the android.permission.READ_PRIVILEGED_PHONE_STATE permission. This prevents potential spoofing by unprivileged third-party apps preloaded on the system partition, guaranteeing the provider is a legitimate system component. I3464b

API Changes

  • Refactored UpdateInfoService to use a secure session model for client interactions. This update enhances security and improves telemetry accuracy by:
    • Identity Validation: Enforcing strict validation of a client's package name and UID when a session is opened to prevent identity spoofing.
    • Session Management: Introducing a dedicated, per-client session interface to safely handle update queries and manage concurrent teardown requests.
    • Automatic Cleanup: Automatically detecting when a client application crashes or terminates unexpectedly, ensuring resources are freed and disconnection telemetry is reliably triggered. I2cf65

Bug Fixes

  • Fix missing symbols issue on iOS when using the NativeSQLiteDriver and dynamically linking to IOS's SQLite library b/434324365.

New Features

  • VerticalTextLayout now supports the horizontal layout, to display special spans in Japanese such as Ruby and Emphasis (Boten).

API Changes

API Changes

  • Make AbstractTraceDriver really abstract, and move the Perfetto implementation into the tracing-wire module. Ie2f59
  • Give more descriptive names to base implementations to avoid using the wrong one. For developers previously extending androidx.tracing.Trace{Sink|Driver} they will now need to switch to using AbstractTrace{Sink|Driver}. I9b46d

Important changes since 1.5.0:

  • Introduced Wear Compose Navigation3 library, which integrates with the Navigation 3 library’s NavDisplay and SceneStrategy components, adding Wear-specific swipe-to-dismiss logic using our new SwipeDismissableSceneStrategy.
  • Added TransformingLazyColumn support for reverseLayout, snapping using TransformingLazyColumnDefaults.snapFlingBehavior and Modifier.minimumVerticalContentPadding, which allows defining a preferred content padding for items in the list when they are at the top or bottom edges.
  • Added new overloads for AlertDialog which use a TransformingLazyColumn for consistency with scrolling in other Material3 screens.
  • Improved curved text rendering, particularly for cursive fonts, with the introduction of text-warping via the new CurvedTextStyle parameter warpOffset, which is turned on by default for API 34 onwards.
  • Added LocalAmbientModeManager, a new CompositionLocal that supports defining different UI and behavior for interactive and ambient modes.
  • For a more complete list of the features introduced in version 1.6.0, see the beta01 release notes

Important changes since 1.3.0:

New features

  • The 1.4.0-beta01 release of Wear ProtoLayout indicates that this release of the library is feature-complete and the API is locked (except where marked as experimental). Wear ProtoLayout 1.4 includes the following new functionalities and APIs:
    • Inlined Image Resources and performance improvements: Introduced an improved resource handling concept where ImageResource can be directly inlined within the layout itself.
    • Material3TileService: Introduced a new, Kotlin-friendly service for creating tiles. It simplifies development by providing a single suspend function to return both tile layout and resources. It automatically manages the MaterialScope and ProtoLayoutScope for better resource handling and performance improvements on faster Tiles loading.
    • Tile Previews Update: Tooling for Tile Previews has been updated to support the new ProtoLayoutScope automatic resource handling, ensuring previews reflect inlined resources correctly without extra configuration.
    • Many Kotlin DSL Improvements: Added specialized Kotlin helpers for Tile and all other APIs needed to build a tile (such as Timeline) to improve the developer experience for Kotlin users.
    • Dynamic Service Switching: Introduced METADATA_GROUP_KEY, allowing developers to group multiple TileService instances in the manifest. This enables dynamic switching between different services that represent the same tile on new OS versions.
    • Tile ID in Updates: Developers can now specify a particular tileId in update requests, allowing for more granular control over which tile instances are refreshed.
    • Increased Compile SDK: To support the new Material3TileService and advanced resource handling, the compileSdk version requirement has been increased to 35.
    • ANR Prevention: Moved the unbinding logic during Tile update requests to a background thread to prevent "Application Not Responding" (ANR) errors.
    • Proper RequiresPermission annotation for heart rate data: Starting from API 36, calling PlatformHealthSources.heartRateBpm or PlatformHealthSources.heartRateAccuracy needs android.health.connect.HealthPermissions.READ_HEART_RATE permission to be granted to the calling App.

Important changes since 1.5.0:

For full details of changes since 1.5.0, see the 1.6.0-beta01 release notes.

New features

The 1.6.0-beta01 release of Wear Tiles indicates that this release of the library is feature-complete and the API is locked (except where marked as experimental). Wear Tiles 1.6 includes the following new functionalities and APIs:

  • Inlined Resource Handling and performance improvements: Tiles now support automatic resource collection through ProtoLayoutScope.
  • Material3TileService: Introduced a new, Kotlin-friendly service for creating tiles. It simplifies development by providing a single suspend function to return both tile layout and resources. It automatically manages the MaterialScope and ProtoLayoutScope for better resource handling and performance improvements on faster Tiles loading.
  • Tile Previews Update: Tooling for Tile Previews has been updated to support the new ProtoLayoutScope automatic resource handling, ensuring previews reflect inlined resources correctly without extra configuration.
  • Many Kotlin DSL Improvements: Added specialized Kotlin helpers for Tile and all other APIs needed to build a tile (such as Timeline) to improve the developer experience for Kotlin users.
  • Dynamic Service Switching: Introduced METADATA_GROUP_KEY, allowing developers to group multiple TileService instances in the manifest. This enables dynamic switching between different services that represent the same tile on new OS versions.
  • Tile ID in Updates: Developers can now specify a particular tileId in update requests, allowing for more granular control over which tile instances are refreshed.
  • Increased Compile SDK: To support the new Material3TileService and advanced resource handling, the compileSdk version requirement has been increased to 35.
  • ANR Prevention: Moved the unbinding logic during Tile update requests to a background thread to prevent "Application Not Responding" (ANR) errors.

API Changes

  • The startUpWebView API and related async startup configuration APIs in ProcessGlobalConfig and WebViewStartUpConfig have been graduated from experimental to stable.
    WebView startup can be a time-consuming process, so these APIs allow applications to trigger WebView startup at the right time, ensuring that portions of WebView startup which are able to run in the background will do so, improving the responsiveness of the first WebView usage.
    These APIs were previously released as experimental, and can now be used without an @OptIn annotation. The previous version of startUpWebView has been deprecated, and users of that API should migrate to the new version, which takes a WebViewOutcomeReceiver to facilitate failure callbacks. Iebb60 I56bf7
  • Navigation APIs no longer require the use of @OptIn annotations.
    This covers WebViewCompat#addNavigationListener, as well as the NavigationListener interface, and the Navigation and Page classes. Note that the Navigation and Page types are now classes instead of interfaces.
    These APIs should now be feature checked using the new WebViewFeature#NAVIGATION_LISTENER feature constant. I410c8 b/474625648 b/448580228 b/479792864 b/432696062 b/474625648
  • Removes the experimental annotation from WebViewCompat#saveState. This API is similar to WebView#saveState, but allows the developer to specify a maximum size for the state, and whether forward history entries should be included. Ie3fe1 b/389076708
  • Profile#setSpeculativeLoadingConfig is deprecated. Use Profile#setMaxPrerenders, PrefetchCache#setMaxPrefetches, PrefetchCache#setPrefetchTtlSeconds instead. I9f0f7 I9b977 b/466301565

Bug Fixes

  • Fix additional issues with network calls failing from background even when network constraint are met Ic7f73 b/445324855
  • Handle security exception in NetworkStateTracker. I4b7ca b/480123154
  • Fixed an issue where periodic WorkRequests that fail due to an uncaught exception would not be rescheduled. Ia6b92 b/443879071

API Changes

  • Changed Config.augmentedObjectCategories from a List to a Set, I25a64 b/487376359
  • Removed unscaledGravityAlignedActivitySpace flag from Session.create. ActivitySpace is always unscaled and gravity-aligned now. If6f11 b/458173423
  • Added Session.create overload to allow passing an Android Context for resource-scoping. I7d3fe b/415805990 b/477386334
  • Added JvmOverloads to FloatSize2d.to3d, Matrix3.copy, and Matrix4.copy I69586 b/481371562
  • Added ability to set categories for AugmentedObject tracking in the Config I1f6e4 b/480220930
  • Added xr:runtime:runtime-interfaces module. I52ac6 b/461561664