Dev Channel Update for ChromeOS / ChromeOS Flex

The Dev channel is being updated to OS version: 15378.0.0, Browser version: 113.0.5635.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

Interested in switching channels? Find out how.

Matt Nelson,

Google ChromeOS

Chrome Beta for Android Update

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

Beta Channel Update for Desktop

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

A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issues, 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.


Srinivas Sista

Improving your security with shorter Session Length defaults

What’s changing 

To further improve security for our customers, we are changing the default session length to 16 hours for existing Google Cloud customers. Note that this update refers to managing user connections to Google Cloud services (e.g. Google Cloud console), not connections to Google services (e.g. Gmail on the web). 


For existing customers who have session length configured to Never Expire, we are updating the session length to 16 hours. See below for more information. 




Who’s impacted 

Admins, end users, and developers 


Why you’d use it 

Many apps and services can access sensitive data or perform sensitive actions. Because of this, managing session length is foundational to cloud security and compliance. It ensures that access to the Google Cloud Platform is finite after a successful authentication, which helps deter bad actors should they gain access to credentials or devices.


Additional details 

Google Cloud session controls 
For existing customers who have session length configured to Never Expire, we are updating the session length to 16 hours. This ensures customers do not mistakenly grant infinite session length to users or apps using Oauth user scopes. After the session expires, users will need to re-enter their login credentials to continue their access. This impacts the following: 

Settings can be customized for specific organizations, and will impact all users within that org. This is a timed session length that expires the session regardless of the user's activity. When choosing a session length, admins have the following options:
  • Choose from a range of predefined session lengths, or set a custom session length between 1 and 24 hours. 
  • Configure whether users need just a password, or require a Security Key to re-authenticate.


Third-party SAML identity providers and session length controls 
If your organization uses a third-party SAML-based identity provider (IdP), the cloud sessions will expire, but the user may be transparently re-authenticated (i.e. without actually being asked to present their credentials) if their session with the IdP is valid at that time. This is working as intended, as Google will redirect the user to the IdP and accept a valid assertion from the IdP. To ensure that users are required to re-authenticate at the correct frequency, evaluate the configuration options on your IdP and review the Help Center article to Set up SSO via a third party Identity provider.


Trusted applications
Some apps are not designed to gracefully handle the re-authentication scenario, which can cause confusing app behavior. Other apps are deployed for server-to-server purposes via user credentials — because they don’t require service account credentials, they are not prompted to periodically re-authenticate.

If you have specific apps like this, and you do not want them to be impacted by session length reauthentication, the org admin can add these apps to the trusted list for your organization. This will exempt the app from session length constraints, while implementing session controls for the rest of the apps and users within the organization.


Getting started

  • Admins: For customers who have their session length set to "Never Expire", your session length will reset to 16 hours. It can be turned off or modified at the OU level. Visit the Help Center article to learn how to set session length for Google Cloud services for your organization.  
  • End users: If a session ends, users will simply need to log in to their account again using the familiar Google login flow. 

Rollout pace

Availability

  • Available to all Google Workspace and Cloud Identity customers, as well as legacy G Suite Basic and Business customers

4 updates from the Google for Games Developer Summit

Posted by Alex Chen, Google for Games

This week, we announced new games solutions and updates to our tools at the Google for Games Developer Summit, a free digital event for developers, publishers and advertisers. From highlighting viewership growth trends on YouTube gaming to reaching more players on different devices with Google Play Games on PC, here’s a quick recap with some of our top announcements and key updates.

1. Build high-quality games on Android

The Android team talked about how they’ve made it easier to develop fun and engaging games with updates to Android vitals and the Android Game Development Kit. They also shared how you can get these games to more users on more devices, with Android support for form factors like foldables, Chromebooks and PCs. Learn more about these announcements, including new ways to connect with a global audience, on the Android Developers blog.

2. Strengthen your ads monetization and growth strategies

Google Ads showed advertisers how to get more value from both in-app ads and in-app purchases with a new feature called target return on ad spend for hybrid monetization. And AdMob showed publishers how to save time and costs with a more efficient way to manage ad mediation, with a revamped buyer management interface and streamlined ad unit mapping workflow. See more in the Google Ads blog post.

3. Create connections with your community

As a home of popular gaming creators, videos, and livestreams worldwide, YouTube continues to see incredible growth. The YouTube team announced that over 2 trillion hours of gaming content was consumed in 2022. Through different formats, availability on multiple devices and culture-shaping Creators, they’re committed to being the place where game publishers and Creators reach players and build communities around their favorite games.

4. Keep players engaged with live service games

Google Cloud shared their strategy for live service game development. They’re combining technology that brings togethers players from all over the world, databases that store critical data for an optimal player experience and the analytics that allow game companies to foster a relationship with their players. Learn more on Google Cloud’s blog.

Whether it’s creating the newest hit game, connecting with an enthusiastic community or growing your business to reach more players everywhere, Google is glad to be your partner along the way. To learn more, you can access all content on demand. And if you’re planning to attend Game Developers Conference next week in San Francisco, come say hi at one of our in-person developer sessions.

Deprecation of Display & Video 360 API v1

Today we are deprecating Display & Video 360 API v1. While deprecated, v1 will no longer be updated. We will sunset v1 on September 14, 2023. Migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about new features available in v2, such as the ability to retrieve YouTube & Partners line items, ad groups, and ads. Follow the steps in our v2 migration guide to help you migrate from v1 to v2.

After supporting and regularly updating Display & Video 360 API v1 for over three years, we are excited to introduce new Display & Video 360 API features using a more consistent version release and sunset schedule. A projected schedule will be announced on this blog at a later date.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team