Dev Channel Update for ChromeOS/ChromeOS Flex

The Dev channel is being updated to 123.0.6312.11 (Platform version: 15786.4.0) for most ChromeOS devices. This build contains a number of bug fixes and security updates.

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.

Daniel Gagnon,

Google ChromeOS 

Conduct direct 1:1 calls with people outside your video calling network on Google Meet mobile

What’s changing

Earlier this year, we introduced cloud-encrypted 1:1 video calls between users in the same domain using the Meet mobile app. In the coming weeks, users from outside of your domain will be able to initiate 1:1 video calls with your users and vice versa. Admins will be able to pre-configure this functionality as on or off for their users with a new admin control. The timeline for this update is as follows:

  • Admin control for restricting external calls placed directly to a user via their email: Admins will begin seeing the new control beginning today. 
  • End user availability: The external calling feature will begin rolling out to end users beginning in April.

Who’s impacted

Admins and end users



Why it matters

1:1 cloud-encrypted video calling in the Meet mobile app makes it easier to connect with others by significantly reducing the need to create meeting links ahead of time. We’re expanding these 1:1 cloud-encrypted calls to allow users outside of your domain to initiate 1:1 calls, making it easier to connect with your external partners and stakeholders. However, to ensure external contact is appropriate, admins can turn this functionality on or off for their users.


Getting started

    • By default, users can receive calls only from contacts and other users in the organization. You can use the new admin switch to enable calls from outside your domain at the OU level. Visit the Help Center to learn more about restricting who can call users in your organization with Google Meet.
      • Note: This setting affects only Google Meet calling, not legacy services (formerly known as Duo) or calling in Google Chat. This also does not affect the ability to join meetings. Visit the Help Center to learn more about turning Meet legacy calling on or off for your users. Note that If you have legacy calling enabled for your users, they will have access to features previously found in Duo (group calls, messages, moments, family mode, etc.) if they have not upgraded to the new Meet app. 

  • End users: 



Rollout pace


Availability

  • Available to all Google Workspace customers

Stable Channel Update for Desktop

The Stable channel has been updated to 122.0.6261.94 for Mac,Linux and 122.0.6261.94/.95 to Windows 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 122.0.6261.94 for Mac and 122.0.6261.95 for Windows 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 4 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[$7000][324596281] High : Type Confusion in V8. Reported by 5f46f4ee2e17957ba7b39897fb376be8 on 2024-02-11

[$7000][323694592] High : Type Confusion in V8. Reported by Bohan Liu (@P4nda20371774) of Tencent Security Xuanwu Lab on 2024-02-05


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:

  • [326980493] 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

Increase Test Fidelity By Avoiding Mocks

This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office.

by Andrew Trenk and Dillon Bly

Replacing your code’s dependencies with mocks can make unit tests easier to write and faster to run. However, among other problems, using mocks can lead to tests that are less effective at catching bugs.

The fidelity of a test refers to how closely the behavior of the test resembles the behavior of the production code. A test with higher fidelity gives you higher confidence that your code will work properly. 

When specifying a dependency to use in a test, prefer the highest-fidelity option. Learn more in the Test Doubles chapter of the Software Engineering at Google book.

  1. Try to use the real implementation. This provides the most fidelity, because the code in the implementation will be executed in the test. There may be tradeoffs when using a real implementation: they can be slow, non-deterministic, or difficult to instantiate (e.g., it connects to an external server). Use your judgment to decide if a real implementation is the right choice.
  2. Use a fake if you can’t use the real implementation. A fake is a lightweight implementation of an API that behaves similarly to the real implementation, e.g., an in-memory database. A fake ensures a test has high fidelity, but takes effort to write and maintain; e.g., it needs its own tests to ensure that it conforms to the behavior of the real implementation. Typically, the owner of the real implementation creates and maintains the fake.
  3. Use a mock if you can’t use the real implementation or a fake. A mock reduces fidelity, since it doesn’t execute any of the actual implementation of a dependency; its behavior is specified inline in a test (a technique known as stubbing), so it may diverge from the behavior of the real implementation. Mocks provide a basic level of confidence that your code works properly, and can be especially useful when testing a code path that is hard to trigger (e.g., an error condition such as a timeout).
    (Note: Although “mocks” are objects created using mocking frameworks such as Mockito or unittest.mock, the same problems will occur if you manually create your own implementation within tests.)

A low-fidelity test: Dependencies are replaced with mocks. Try to avoid this.

A high-fidelity test: Dependencies use real implementations or fakes. Prefer this.

@Mock OrderValidator validator;

@Mock PaymentProcessor processor;

...


ShoppingCart cart =

new ShoppingCart(

validator, processor);

OrderValidator validator =

createValidator();

PaymentProcessor processor =

new FakeProcessor();


...


ShoppingCart cart =

    new ShoppingCart(

validator, processor);

Aim for as much fidelity as you can achieve without increasing the size of a test. At Google, tests are classified by size. Most tests should be small: they must run in a single process and must not wait on a system or event outside of their process. Increasing the fidelity of a small test is often a good choice if the test stays within these constraints. A healthy test suite also includes medium and large tests, which have higher fidelity since they can use heavyweight dependencies that aren’t feasible to use in small tests, e.g., dependencies that increase execution times or call other processes.

Chrome Stable for iOS Update

 Hi everyone! We've just released Chrome Stable 122 (122.0.6261.89) 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.

Erhu Akpobaro
Google Chrome

New ways to annotate Google Docs

What’s changing

We’re excited to announce a new feature, markups in Google Docs, which gives you more flexibility when providing feedback in a document. The new markups experience lets you add handwritten annotations to documents with a stylus or your finger when using an Android device. 

Markups can be useful in numerous scenarios, such as: 
  • Colleagues giving each other handwritten feedback on diagrams, charts, reports or proposals. 
  • Educators giving students feedback on their essays, reports, short stories and more. 
  • A homeowner providing ideas or updates on construction plans from their contractor. 
In order to add annotations, you must use an Android device. From there, you can: 
  • Enter the markups mode and annotate using pen or highlighter tools 
  • Hide/show markups 
  • Erase markups 
  • Insert suggested markups 
Markups on Android


On iOS devices, you can: 
  • View a document with markups 
  • Delete markups 
  • Hide/show markups 
markups on iOS

On desktop, you can: 
  • View a document with markups 
  • Delete markups 
  • Hide/show markups 
markups on desktop

Getting started 

  • Admins: There is no admin control for this feature. 
  • End users: To turn on markups, open a document > select the markups tool from the contextual toolbar > draw with your finger or stylus. 

Rollout pace 


Availability 

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

Chrome Stable for iOS Update

Hi everyone! We've just released Chrome Stable 122 (122.0.6261.89) 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.

Erhu Akpobaro
Google Chrome

Available in open beta: the Groups Admin role can now be provisioned for specific group types

What’s changing

The Groups Admin role can now be assigned for security groups or non-security groups. Previously, those with the Groups Admin role had access to all groups within an organization. This change gives administrators more granular delegation of group admin responsibilities, helping limit access to the most sensitive groups to only those who absolutely need it. 

This feature is available in open beta, which means no additional sign-up is required to use the feature.

Getting started

Easily identify which unread threads are most relevant to you in Google Chat

What’s changing 

Last year, we announced that all newly created spaces in Google Chat will be in-line threaded. This streamlined user experience enables you to reply to any message and create a separate discussion isolated from the main conversation. We also introduced several updates, such as home, mentions and starred messages to help you find what you need much faster in Chat.

Today, we’re continuing our enhancements across Chat by improving the in-line threaded experience in spaces. With multiple threads across numerous spaces, we know it can be difficult to identify which unread threads are most relevant to you. In order to provide you with more context upfront, you will now see participant avatars for unread threads in the conversation view. Without having to click to open the thread side panel, it will now be much easier to decide which threads to read and reply to. 
Web experience


Who’s impacted 

End users 


Why you’d use it 

Being able to see the participant avatars for unread threads makes it easier to identify whether a thread is relevant to you. 
mobile experience



Getting started 

  • Admins: There is no admin control for this feature. 
  • End users: This will be ON by default. Visit the Help Center to learn how to use Google Chat

Rollout pace 

Web: 
Android:
iOS:

Availability 

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

Resources 

New goodies from Android, Wearables at Mobile World Congress + tune in to a new episode of #TheAndroidShow next week!

Posted by Anirudh Dewani, Director of Android Developer Relations

Earlier today, at Mobile World Congress (MWC), an annual conference showcasing the latest in mobile, Android and our partners unveiled a range of new goodies, including new wearables, foldables, as well as a number of new features for Android users. Keep reading below to see how you, as developers, can take advantage of these new features and devices that are being released. And in just over a week, on Thursday March 7 at 10AM PT, we’ll be kicking off another episode of #TheAndroidShow, our quarterly live show on YouTube and on developer.android.com, where we’ll dive more into these topics.


Meet the new watch from OnePlus and how we’re boosting power with the Wear OS hybrid interface

Wearables are on display across MWC this week, and one of our favorites is OnePlus Watch 2, powered with the latest version of Wear OS (Wear OS 4). As part of our ongoing work to improve the Wear OS by Google user experience, we’ve made fundamental changes to the platform and substantially expanded the capabilities of the Wear OS hybrid interface that improve two key areas: power and performance. As a developer, you can leverage existing Wear OS APIs to get underneath optimizations without any added effort – no code changes required! You can read more about the updates here.

Images of three people wearing the OnePlus Watch 2

A few new features for Android users

Google released 9 new features Android users can take advantage of across Google apps, you can read more about those features here. For developers, we wanted to highlight a few ways you can take advantage of this news across experiences you build into your apps:

    • More places for users to see their Health Connect data, now in the Fitbit app: With permission from your users, Health Connect is a central way to connect and sync their favorite health and fitness apps, see all their data in one place, and stay in control of their privacy. By setting up Health Connect in the Fitbit mobile app for Android, users will have an overview of their health and fitness data from across their apps in one place. You can join developers like Peloton, ŌURA, and Lifesum who are using Health Connect to provide their users with deeper health and fitness insights, get started now!
Image that reads 'New updates on Android' with pictures of a smart watch, laptop, and Android Auto

A new episode of #TheAndroidShow, live on March 7 at 10AM PT. Send us your #AskAndroid questions now!

You can join us on March 7 at 10AM PT for a new episode of #TheAndroidShow. In this quarterly show, we’ll unpack the latest Android foldables and large screens for you to get building on, plus a behind-the-scenes on Gemini Nano and AICore.

We’ll have a live #AskAndroid Q&A with the team about building Android; you can ask us about building excellent apps across devices, Android 15, Compose, Gemini and more, using #AskAndroid on X or on YouTube. Our experts are ready to answer your questions live!

#TheAndroidShow: March 7 at 10AM PT, broadcast live on YouTube and d.android.com/events/show!