Chrome Dev for Desktop Update

The Dev channel has been updated to 128.0.6585.0 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.

Prudhvi Bommana
Google Chrome

Access Google Meet artifacts with a new Google Drive API scope

What’s changing 

We’re introducing a new OAuth scope for the Drive API: drive.meet.readonly. The new scope grants app access to read and download files from a user’s drive that were created or edited by Google Meet — this includes meeting transcripts, notes, recordings, and more. This granular level of authorization helps ensure Drive access is not provisioned too broadly and only the necessary files can be accessed.


Getting started

Rollout pace


Availability


Reminder: Entity Read Files sunset on October 31, 2024

On October 31, 2024, Display & Video 360 Entity Read Files (ERFs) will sunset. After this date, new private and public ERFs will not be generated. ERFs were deprecated in June 2021 and the October sunset date was first announced in January 2024.

If you are currently using ERFs to programmatically retrieve Display & Video 360 resource configurations, migrate to the Display & Video 360 API. You can either integrate directly with the Display & Video 360 API using REST requests or automatically import Display & Video 360 resource configurations into BigQuery using the Display & Video 360 API BigQuery Connector.

See our migration guide for more information on migrating to the Display & Video 360 API and the two integration options.

If you have questions or concerns about this migration, please contact us using our new Display & Video 360 API Technical support contact form.

Reduce ANRs when implementing mobile ads

We heard your feedback via Play Console crash reports regarding Application Not Responding (ANRs) errors related to the Google Mobile Ads SDK. After analyzing these reports, we updated our SDK implementation best practices to reduce ANR rates. The recommended best practices are as follows:

  1. Initialize the Mobile Ads SDK on a background thread
  2. Enable optimization flag for ad loading

1. Initialize the Mobile Ads SDK on a background thread

Our previous best practice was to specify the OPTIMIZE_INITIALIZATION manifest flag. However, some work on the calling thread is still required to prepare MobileAds to handle other method calls synchronously.

We now recommend calling MobileAds.initialize() on a background thread, enabling the work required on the calling thread to happen in the background.

import com.google.android.gms.ads.MobileAds
import kotlinx.coroutines.CoroutineScope
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.launch

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)

    CoroutineScope(Dispatchers.IO).launch {
      // Initialize the Google Mobile Ads SDK on a background thread.
      MobileAds.initialize(this@MainActivity) {}
      runOnUiThread {
        // Load an ad on the main thread.
        loadAd()
      }
    }
  }
}

Note: When calling MobileAds.initialize() on a background thread, the OPTIMIZE_INITIALIZATION manifest flag is no longer required.

2. Enable optimization flag for ad loading

By enabling the OPTIMIZE_AD_LOADING manifest flag, you can offload most ad loading tasks to a background thread. We recommend enabling this flag in your app's AndroidManifest.xml file to reduce the occurrence of ad loading causing ANRs.

<manifest>
  ...
  <application>
      ...
      <meta-data
          android:name="com.google.android.gms.ads.flag.OPTIMIZE_AD_LOADING"
          android:value="true"/>
  </application>
</manifest>

We’ve updated all of our Android example apps to implement these best practices. For more details on initialization and optimization flags, see Get started and Optimize initialization and ad loading. Contact us if you have any questions or need additional help.

Rollout Update: setting the default camera framing option for Google Meet hardware devices

What’s changing 

We recently announced several updates related to framing options on Google Hardware devices. This included the ability for admins to configure the default camera framing option for their hardware devices. After pausing rollout to optimize performance, we are pleased to announce that this feature is now fully available.


Getting started


Availability

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources


Chrome Beta for Desktop Update

The Beta channel has been updated to 127.0.6533.43 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.

Daniel Yip
Google Chrome