Hello Everyone! We've just released Chrome 152 (152.0.7977.42) for Android to a small percentage of users. It'll become available on Google Play over the next few days. You can find more details about early Stable releases here.

The Stable channel has been updated to 152.0.7977.42/.43 for Windows and Mac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log.

The legacy automigrations are divided into two separate phases:

• Phase 1 (Campaign-level Broad Match and Automatically Created Assets), which starts September 1, 2026.
• Phase 2 (Dynamic Search Ads), which has been rescheduled to February 2027.

1. Campaign broad and ACA auto-migration: September 1 – September 30, 2026

On September 1, 2026, Google Ads will begin automatically upgrading Search campaigns using Campaign-level Broad Match (CB) or standalone Automatically Created Assets (ACA) to AI Max. The migration job will roll out progressively throughout the month.

To find the campaigns that have been migrated at any point during the month:

   SELECT
      campaign.id,
      campaign.name,
      campaign.aca_migration_date_time,
      campaign.broad_match_migration_date_time
    FROM campaign
    WHERE campaign.aca_migration_date_time > '1970-01-01 00:00:00'
      AND campaign.broad_match_migration_date_time > '1970-01-01 00:00:00'

Default migrated configurations

To support campaign management continuity and minimize performance volatility, campaigns will be migrated in-place to equivalent AI Max settings.

• Campaign-Level Broad Match (CB):
  • Text Customization (TC): OPT_OUT (OFF)
  • Final URL Expansion (FUE): OPT_OUT (OFF)
  • Search Term Matching (STM): true (ON) by default
  • Brand Lists: Existing brand inclusions and exclusions are preserved and moved into the new setup in-place.
• Standalone Automatically Created Assets (ACA):
  • Text Customization (TC): OPT_IN (ON) by default
  • Final URL Expansion (FUE): OPT_OUT (OFF)
  • Search Term Matching (STM): true (ON) by default

2. API creation blocks and legacy cleanup

To prevent the creation of new legacy structures ahead of the auto-migration, strict enforcement blocks are now in place across the developer surfaces:

• Legacy creation end of life (August 3, 2026): Creating new Campaign-level Broad Match configurations or legacy Automatically Created Assets (ACA) is now blocked across the UI, Google Ads Editor, and all versions of the API.

3. API versioning lifecycle and support grace period

How you manage these features depends on the API version your integration targets:

New API versions (post-September 1, 2026)

Any new versions of the Google Ads API released after September 1, 2026, will completely remove the legacy entities used to create or manage:

• Campaign-level Broad Match settings
• Automatically Created Assets

Older API versions (grace period)

• Active support: Previously released API versions that are currently active will temporarily continue to support legacy ACA and Broad Match settings.
• Sunset timeline: You can continue to edit and manage these legacy setups through older API versions until those specific versions reach their standard scheduled sunset (typically one year after their introduction, around September 2027). At that point, all remaining legacy entities will be permanently removed.

4. Dynamic Search Ads automigration February 2027

Your active legacy DSA campaigns are excluded from the September auto-migrations and will continue to serve as normal. However, prepare for the upcoming DSA timeline:

• September 2026: Google will launch in-account pre-migration banners in the UI to warn unmigrated advertisers of the upcoming transition and encourage voluntary one-click upgrades by selecting “Upgrade Your Dynamic Search Ads (DSAs) to AI Max” under Campaign Settings | Dynamic Search Ads setting.
• January 15, 2027: Official MSA reminder notification will be sent to all impacted accounts.
• February 1–28, 2027: Automigration begins. The ability to create new DSA ad groups will be permanently removed, and unmigrated DSA campaigns will automatically upgrade to standard Search ad groups with AI Max enabled.

Developer action plan

1. Audit your integration: Identify any scripts, external tools, or client libraries still attempting to create or edit campaign-level broad match settings or legacy ACA.
2. Move to standard entities: Begin updating your campaign construction workflows to use standard Search campaigns with the AI Max settings bundle (Uber Toggle, Text Customization, and Search Term Matching).
3. Handle grandfathered read-only entities: Be prepared to handle API error codes if your integration attempts to modify (rather than pause or delete) legacy Expanded Dynamic Search ads (eDSAs) or criteria once they transition to standard ad groups.

Bob Hancock, Google Ads API Team

The Beta channel has been updated to 152.0.7977.42 for Windows, Mac and Linux.

A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Chrome Release Team
Google Chrome

One-handed gestures offer a convenient and touch-free way for users to interact with their watches, enabling them to perform key actions using only the hand on which the device is worn. 

First introduced on Pixel Watch with Wear OS 6.1, one-handed gestures made quick interactions effortless, such as starting and stopping a timer, accepting calls, and controlling media. 

Now, with Wear OS 7, we're expanding this functionality with a new Gestures framework that allows OEMs to map gestures to primary actions and dismissals, and an API to bring gesture control to the developer community.

Starting with the 1.7 beta release of Compose for Wear OS, you can seamlessly integrate gesture control into your Wear Compose apps. To use this release, upgrade your Wear Compose dependency to:

androidx.wear.compose:compose-material3:1.7.0-beta01

Designing for one-handed interaction

The one-handed gestures framework is designed around two primary interaction patterns that allow users to take action without touching the screen:

• Primary action, which on Pixel Watch is mapped to a double-pinch gesture: this action should be mapped to the most important task in a given context. For example, users can perform this gesture to take a photo in a camera app, start/stop a timer, or accept an incoming call. 
• Dismiss action, which on Pixel Watch is mapped to a wrist turn gesture: this action is mapped to system back by default and provides an intuitive way to close interruptive screens or get back to the watch face. It may be overridden for specific use cases, such as silencing an incoming phone call.

These gestures are currently available on Pixel Watch 3 and newer, and the Wear OS gesture framework is available to all Wear OS device manufactures to adopt.

Check out our new design guidance for integrating one-handed gestures into your Wear app.

Integrating gestures with Compose on Wear OS

To provide seamless gesture support in Wear OS 7, we are introducing a new Modifier.oneHandedGesture that you can apply to any existing interactive composable to make it gesture-aware. 

Implementing gestures with Compose on Wear OS requires these steps:

1. Define the gesture configuration. Start by using rememberOneHandedGestureConfiguration to define the nature of the interaction. This configuration dictates the basic behavior by providing the GestureAction (e.g. tracking a primary pinch or a dismiss wrist flick).
2. Initialize the indicator state. Depending on your UI component, initialize a specific state object, such as OneHandedGestureClickIndicatorState for buttons or OneHandedGestureScrollIndicatorState for scrollable lists. This state is used to coordinate visual feedback between the gesture detection modifier and the visual UI indicators, seamlessly managing visibility, timing, and animations.
3. Apply Modifier.oneHandedGesture to your interactive component. You'll pass in your configuration and state, and you’ll provide standard callbacks: onGestureAvailable to activate the visual hint when the system prepares the gesture, and onGesture to execute your action when the gesture happens.

The following sample shows how those three steps translate into code when configuring an IconButton:

val gestureConfig = rememberOneHandedGestureConfiguration(action = OneHandedGestureAction.Primary)
val indicatorState = remember { OneHandedGestureClickIndicatorState() }
val coroutineScope = rememberCoroutineScope()

OutlinedIconButton(
    onClick = onPlayPauseButtonClicked,
    modifier = Modifier.touchTargetAwareSize(IconButtonDefaults.LargeButtonSize)
        .oneHandedGesture(
            gestureConfiguration = gestureConfig,
            interactionSource = interactionSource,
            onGestureLabel = "play or pause",
            onGestureAvailable = { 
                coroutineScope.launch { indicatorState.showIndicator() } 
            },
            onGesture = onPlayPauseButtonClicked,
        ),
) {
    // button content goes here
    // See "Guided discovery with gesture indicators" section of this post for recommendations on adding a gesture indicator.
}

The GestureAction.Primary can also be used to scroll when the content is the end goal of the user journey, or there is a gesture actionable button off screen that the user can scroll to. Some examples include:

• Scrolling through a notification to view the content and/or initiate a reply (available in TransformingLazyColumn and ScalingLazyColumn).
• Paging through workout metrics or other content that doesn’t require the user to tap to continue the user journey (available in  HorizontalPager and VerticalPager).  

val scrollGestureConfig = rememberOneHandedGestureConfiguration(action = GestureAction.Primary)
val scrollIndicatorState = remember { OneHandedGestureScrollIndicatorState() }
val coroutineScope = rememberCoroutineScope()

TransformingLazyColumn(
    state = scrollState,
    contentPadding = contentPadding,
    modifier = Modifier
        .fillMaxSize()
        .oneHandedGesture(
            gestureConfiguration = scrollGestureConfig,
            onGestureLabel = "scroll",
            onGestureAvailable = { 
                coroutineScope.launch { scrollIndicatorState.showIndicator() } 
            },
            onGesture = { OneHandedGestureDefaults.scrollDown(scrollState) }
        )
) {
    // list content goes here
    // See "Guided discovery with gesture indicators" section of this post for recommendations on adding a gesture indicator.
}

Guided discovery with gesture indicators

To help users learn which gestures are available, gesture indicators work as hints to help discovery about which gestures are available on a screen.

These hints provide animated cues that inform users where they can perform a gesture. The framework manages the cadence and appearance of these hints, ensuring that they are helpful without being intrusive. System settings let users change the cadence to something less frequent if desired.

To integrate with hints, the API provides the following gesture indicator components:

• the OneHandedGestureClickIndicator for components like a  Button
• the OneHandedGestureScrollIndicator component for scrolling
• the OneHandedGestureHorizontalPageIndicator for the HorizontalPager
• the OneHandedGestureVerticalPageIndicator for the VerticalPager

The following example shows how to use the OneHandedGestureClickIndicator for a Button. See another example for using the OneHandedGestureScrollIndicator in our guidance.

val gestureConfig = rememberOneHandedGestureConfiguration(action = GestureAction.Primary)
val indicatorState = remember { OneHandedGestureClickIndicatorState() }
val coroutineScope = rememberCoroutineScope()

OutlinedIconButton(
    onClick = onPlayPauseButtonClicked,
    modifier = Modifier.touchTargetAwareSize(IconButtonDefaults.LargeButtonSize)
        .oneHandedGesture(
            gestureConfiguration = gestureConfig,
            interactionSource = interactionSource,
            onGestureLabel = "play or pause",
            onGestureAvailable = { 
                coroutineScope.launch { indicatorState.showIndicator() } 
            },
            onGesture = onPlayPauseButtonClicked,
        ),
) {
    OneHandedGestureClickIndicator(
        gestureConfiguration = gestureConfig,
        indicatorState = indicatorState,
    ) {
        val icon = if (playerUiModel.playbackState.isPlaying) Icons.Filled.Pause else Icons.Filled.PlayArrow
        Icon(icon, contentDescription = "Play or Pause")
    }
}

Sample app showing gesture hint for media controls

We are already seeing early adoption of these APIs from partners like Spotify, who are using one-handed gestures to make music control more seamless on the go. By adopting the Modifier.oneHandedGesture into their Wear OS app, Spotify allows users to play or pause their music with the primary gesture action, which on Pixel Watch devices is the double-pinch gesture. This action triggers the same behavior as the physical play/pause button, and the user doesn’t  need to touch the screen.

. 

Bring one-handed gestures to your app

You can begin experimenting with one-handed gestures today in the 1.7 beta release of Compose for Wear OS.

Ensure your app is running on Wear OS 7, which provides the underlying platform support for gesture detection. Check out our new one-handed gestures developer guide  to see how you can start building more convenient experiences for your users.

Hi everyone! We've just released Chrome Stable 152 (152.0.7977.40) for iOS; it'll become available on App Store in the next few hours.

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Chrome Release Team
Google Chrome

Hi everyone! We've just released Chrome Beta 152 (152.0.7977.42) for Android. It's now available on Google Play.

You can see a partial list of the changes in the Git log. For details on new features, check out the Chromium blog, and for details on web platform updates, check here.

If you find a new issue, please let us know by filing a bug.

Chrome Release Team
Google Chrome