Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 129 (129.0.6668.38) 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.

Krishna Govind
Google Chrome

Google Meet Add-ons SDK is now generally available

What’s changing 

We’re pleased to announce that beginning today, the Meet Add-ons SDK is now generally available for the web. This SDK allows developers to iframe their app into Meet, and lets meeting participants interact with the app’s content directly inside the Meet canvas. 

Meet Add-ons SDK example with Miro

Who’s impacted 

Admins, end users, and developers 


Why it matters 

The Add-ons SDK expands Meet’s existing platform capabilities, providing the opportunity for developers to build interactive and collaborative experiences for their users in Google Meet which they can find and install from the Google Workspace Marketplace. These experiences allow for users to launch, install, and engage with the app’s content during their meetings, all without ever leaving Google Meet. Examples of already built add-ons include whiteboarding experiences with Figjam, Lucidspark and Miro; note taking experiences with Read Notetaker; and also polling and surveying experiences via Polly. 

Add-ons can be displayed in two ways during a meeting: 
  1. The main stage allows apps to be the focal point of a meeting experience, unlocking the opportunity for add-on users to supercharge collaboration while in a meeting. 
  2. The side panel allows users to do actions such as share data, take surveys, or update records and notes while keeping the meeting and the discussion with other participants the focal point of this experience. 

Add-ons can be displayed in two ways during a meeting: main stage or side panel

Additional details 

The Google Workspace Marketplace automatically respects any controls that have been configured by admins, including whether their users can download and install add-ons. Additionally, all apps on the Marketplace have been reviewed and approved by the Google Marketplace team before they’re published. 


Getting started 

  • Admins: The availability of Google Meet Add-ons in meetings can be controlled through the Google Meet Admin Controls. Visit the Help Center to learn more about admin controls for Add-ons. 
  • Developers: Our Developer Documentation has more information about using the Meet Add-Ons SDK. 
  • End users: 
    • Visit the Help Center to learn more about using add-ons with Google Meet. 
    • Meeting hosts can control the availability of add-ons during meetings by going to Host Controls (lock icon) > Meeting Activities > Let contributors share add-on activities. Refer to this announcement on the Workspace Updates blog for more information. 

Rollout pace 

Availability 

  • Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts

Resources 

Chrome for Android Update

Hi, everyone! We've just released Chrome 128 (128.0.6613.146) for Android . It'll become available on Google Play over the next few days. 

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.

Android releases contain the same security fixes as their corresponding Desktop (Windows & Mac: 128.0.6613.137/138 and Linux:128.0.6613.137) unless otherwise noted.


Harry Souders
Google Chrome

Stable Channel Update for Desktop

The Stable channel has been updated to 128.0.6613.137/.138 for Windows, Mac and 128.0.6613.137 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.

The Extended Stable channel has been updated to 128.0.6613.138 for Windows and Mac which will roll out over the coming days/weeks.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.


This update includes 5 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[$15000][361461526] High CVE-2024-8636: Heap buffer overflow in Skia. Reported by Renan Rios (@hyhy_100) on 2024-08-22

[$11000][361784548] High CVE-2024-8637: Use after free in Media Router. Reported by lime(@limeSec_) from TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-08-23

[TBD][362539773] High CVE-2024-8638: Type Confusion in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-08-28

[TBD][362658609] High CVE-2024-8639: Use after free in Autofill. Reported by lime(@limeSec_) from TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-08-28


We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:

  • [365619166] Various fixes from internal audits, fuzzing and other initiatives


Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.


 

Interested in switching release channels? Find out how here. 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.


Prudhvikumar Bommana
Google Chrome

Dev Channel Update for ChromeOS / ChromeOS Flex

The Dev channel is being updated to OS version: 16026.0.0,  Browser version: 130.0.6703.0, for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:

  1. File a bug
  2. Visit our ChromeOS communities
    1. General: Chromebook Help Community
    2. Beta Specific: ChromeOS Beta Help Community
  3. Report an issue or send feedback on Chrome
  4. Interested in switching channels? Find out how.


Giuliana Pritchard,
Google ChromeOS 

Google Cloud Directory Sync now complies with your conflicting accounts management settings

What’s changing 

When Google Cloud Directory Sync (GCDS) attempts to create new users, it may encounter unmanaged accounts that conflict with the accounts it’s attempting to create. In these instances, GCDS will now comply with the conflicting accounts management settings specified in the Admin console. This update helps reduce the time spent migrating user accounts to business accounts, helping to accelerate the adoption of Google Workspace and Google Cloud. Visit the Help Center for specific information on how GCDS will handle conflicting accounts based on your configured settings. 

Getting started 

  • Admins: Google Cloud Directory Sync will automatically respect your existing Admin console settings for handling conflicting unmanaged accounts. We do not recommend turning this feature off in GCDS, rather you should configure these settings as you see fit in the Admin console. Visit the Help Center to learn more about handling conflicting unmanaged accounts with Google Cloud Directory Sync, as well as unmanaged accounts in general. 
  • End users: Depending on your admin configuration: 
    • You’ll be invited to transfer your account — if accepted, your admin will have the ability to manage your account. 
    • If you do not accept the request, your admin may replace your unmanaged account with a managed one. In that case, you’ll receive a new @gmail.com address and retain your content in this unmanaged, personal Google account. 

Rollout pace


Availability

  • Available for all Google Workspace customers 

 Resources 

Access and sort shared files more easily in Google Chat conversations

What’s changing 

Earlier this year, we improved upon the file management experience in Google Chat spaces by creating the Shared tab, a central place to manage all conversation-related artifacts including files, links and media. Today, we’re excited to announce that the Shared tab is now available in 1:1 direct messages and group messages, enabling easier collaboration across all conversation types. 
Shared tab is now available in 1:1 direct messages and group messages

Who’s impacted 

End users 


Why you’d use it 

The Shared tab provides a centralized and visible method to access shared content shared within a conversation. 


Additional details 

Using the new sort drop-down, you can narrow down the list of documents displayed based on category (file, link, media) or date shared. 


Getting started

  • Admins: There is no admin control for this feature. 
  • End users: At the top of a Google Chat message, you will see the following tabs: Chat and Shared. Upon clicking Shared, you will see three sections: Files, Links and Media. Visit the Help Center to learn more about sending & sharing files in Google Chat messages. 

Rollout pace 

Web: 
Android & iOS: 

Availability 

  • Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts 

Resources