Announcing iOS Google Mobile Ads SDK Version 12.0.0

Version 12.0.0 of the Google Mobile Ads SDK is now available. We recommend upgrading as soon as possible to get our latest features and performance improvements.

Updated Swift APIs

We’ve updated the Google Mobile Ads SDK to define an NS_SWIFT_NAME for every API to follow the naming conventions from Apple’s Swift API Design Guidelines. For example, we have:

  • Removed the GAD prefix across names for all types.
  • Renamed the GAM prefix to AdManager.
  • Renamed the GADM prefix to Mediation.

For the full list of Swift API name changes, see Swift naming support.

Swift 6 Concurrency

Swift 6 concurrency support is being rolled out incrementally, starting this release with added support for our ad format delegate methods. Future SDK versions will include further improvements.

Changes to Xcode requirements

The minimum supported Xcode version has been bumped to 16.0.

For the full list of changes, check the release notes. Check our migration guide to ensure your mobile apps are ready to upgrade.

SDK Deprecation Reminder

Per the deprecation schedule, the release of version 12.0.0 means that:

  • iOS Google Mobile Ads SDK versions 10.x.x are officially deprecated, and will sunset in Q2 2026.
  • Versions 9.x.x and below will sunset on June 30, 2025.
    • While there are currently no plans to disable ad serving on version 9.x.x, we strongly recommend updating to a supported SDK version to avoid being impacted in the future.

As always, if you have any questions or need additional help, contact us via the developer forum.

Google Workspace Updates Weekly Recap – February 7, 2025

3 New updates

Unless otherwise indicated, the features below are available to all Google Workspace customers, and are fully launched or in the process of rolling out. Rollouts should take no more than 15 business days to complete if launching to both Rapid and Scheduled Release at the same time. If not, each stage of rollout should take no more than 15 business days to complete.




Insert responses from Gemini directly into email drafts in the Gmail app
Last year, we introduced the ability for users to ask Gemini questions about their inbox or do things like find specific details in their emails, show unread messages, and more through Gmail Q&A on iOS and Android devices. To build upon this, users can now quickly insert responses or content received after asking Gemini a question directly into an email draft. To do so, open Gemini in the Gmail app (via the Gemini spark at the top right or from a “summarize this email” chip) > ask Gemini a question about the email or your inbox > insert the response by tapping the insert arrow on Android or “Insert” button on iOS. | Rollout to Rapid Release and Scheduled Release domains is complete. | Available to Google Workspace Business and Enterprise users with access to Gemini in Gmail. | Visit the Help Center to learn more about Gemini in Gmail.

Insert responses from Gemini directly into email drafts in the Gmail app

Improving Google Chat app commands 
Currently, you can use slash commands in Google Chat messages to communicate quickly with apps. To simplify this process, we’re excited to introduce quick commands, a way for users to invoke an app command directly without typing a slash command. Developers should use this resource to learn how to set up and respond to quick commands for their Google Chat app. When users invoke a quick command, your Chat app receives an APP_COMMAND interaction event, instead of the MESSAGE interaction event that is sent for slash commands. To modify an existing slash command into a quick command, please follow these steps. After a developer configures quick commands through the Chat API configuration page, users can access them by clicking the plus button menu next to the Chat compose box and then selecting their desired quick command. | Rolling out now to Rapid Release and Scheduled Release domains at an extended pace (potentially longer than 15 days for feature visibility), with expected completion by March 3, 2025. | The ability to configure app commands is available to all Google Workspace customers. | The ability to use app commands is available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts. | Visit this developer documentation to learn more about quick commands for Chat apps.


adding quick commands to google chat apps

The ability to generate images with people powered by Imagen 3 is now available across Workspace
We recently upgraded our AI image generation in Workspace to the latest version of Imagen 3, delivering richer details and textures to help bring your creative vision to life. Today, we’re excited to announce that you can now use this technology as you generate images of people in:


Rollout for generating images with people is complete for Gemini Advanced. | Rollout for generating images with people using Gemini in the side panel of Docs, Sheets, Drive, Slides, Gmail, and Vids is complete (in English only). | Rollout for generating images with people for the Gemini app is expected to complete by March 1, 2025. | Available to all Google Workspace users accessing the Gemini app or Gemini Advanced. | Visit the Help Center to learn more about accessing the Gemini app with your Workspace account.



Previous announcements

The announcements below were published on the Workspace Updates blog earlier this week. Please refer to the original blog posts for complete details.


Now generally available: improved syncing experience between Google Calendar and third-party calendars 
In June of 2024, we introduced an improved email notification experience between Google Calendar and third-party calendar services, like Outlook, via beta. Beginning this week, this update is now generally available. | Learn more about improved syncing between Google Calendar and third-party calendars. 

Additional improvements to everyday actions in Google Sheets 
This week, we announced additional improvements available for everyday actions in Sheets: 1) pasting data is now up to 50% faster when you’re pasting from one spreadsheet to another, 2) filter conditions can now be set up to 50% faster than before, and 3) spreadsheets now load existing data up to 30% faster. | Learn more about Sheets improvements. 

Google Meet adds more screen reader options for in-meeting reactions
To improve access for users with vision disabilities, we are adding several more options for how reactions in Google Meet are experienced through screen readers. You can access and adjust the settings at any time during the meeting by pressing Shift+R or from the Settings menu (Three-dot overflow button > Settings > Reactions > Accessibility). | Learn more about screen reader options. 

Developers can now add form field validation to Google Workspace add-ons and Google Chat app cards 
Workspace add-ons and Chat app developers can add client-side input validation to Chat apps and add-ons. | Learn more about adding form field validation to add-ons and app cards. 

Know who an event is shared with when using shared Google Calendars 
Users with the ability to “Make changes to events” can now see the members of the shared calendar, i.e. who their events are shared with. | Learn more about using shared Google Calendars. 

Now generally available: Easily migrate files from Microsoft OneDrive to Google Drive 
In October 2024, we expanded our data migration services to include the ability for Admins to transfer OneDrive data to Google Drive. This functionality is now generally available. You can migrate the files of up to 100 users at a time, including the files corresponding access permissions with shared members. | Learn more about migrating files.

NotebookLM and NotebookLM Plus now available as a Google Workspace core service with enterprise-grade data protection
NotebookLM and NotebookLM Plus, previously introduced as additional services, are now included as core services for Workspace Business and Enterprise customers. Covered under your Google Workspace terms of service, these apps offer the same enterprise-grade data protections and level of technical support as other Workspace core services. | Learn more about NotebookLM and NotebookLM Plus.

Easily convert data to people chips and update chip format in Google Sheets
Similar to the functionality in Google Sheets that helps you easily convert data to dropdown chips, you can now use bulk chip conversion for people chips. | Learn more about chips in Sheets.

Google Vault now supports the Gemini app
Google Vault now supports the Gemini app (on web and mobile). Going forward, admins can use Vault for eDiscovery tasks to search Gemini app conversations and create an export of your search results. | Learn more about Vault supporting the Gemini app.


Completed rollouts

The features below completed their rollouts to Rapid Release domains, Scheduled Release domains, or both. Please refer to the original blog posts for additional details.


Rapid Release Domains: 
Scheduled Release Domains: 
Rapid and Scheduled Release Domains: 


    For a recap of announcements in the past six months, check out What’s new in Google Workspace (recent releases).
        

    Long Term Support Channel Update for ChromeOS

    A new LTS-126  version 126.0.6478.264 (Platform Version: 15886.89.0), is being rolled out for most ChromeOS devices. 



    This version includes selected security fixes including:

    378623799  High CVE-2025-0437 Out of bounds read in Metrics

    384186539  High CVE-2025-0438  Security: Stack buffer overflow in Tracing

    Release notes for LTS-126 can be found here 

    Want to know more about Long-term Support? Click here

    Andy Wu

    Google ChromeOS

    Timeline update: third-party autofill services support on Chrome on Android

    Posted by Eiji Kitamura – Developer Advocate (@agektmr)

    In October 2024, we announced that Chrome 131 will allow third-party autofill services on Android (like password managers) to natively autofill forms on websites. Reflecting on feedback from autofill service developers, we've decided to shift the schedule and allow the third-party autofill services from Chrome 135.

    Native Chrome support for third-party autofill services on Android means that users will be able to use their preferred password manager or autofill service directly in Chrome, without having to rely on workarounds or extensions. This change is expected to improve the user experience and security for Android users who use third-party autofill services.

    Based on developer feedback, we've fixed bugs, and have been working to make the new setting easier to discover. To support those goals, we've added the following capabilities:

      • An ability to query Chrome settings and learn whether the user wishes to use a third party autofill service
      • An ability to deep link to the Chrome settings page where users can enable third-party autofill services.

    Read Chrome settings

    Any app can read whether Chrome uses the 3P autofill mode that allows it to use Android Autofill. Chrome uses Android's ContentProvider to communicate that information. Declare in your Android manifest which channels you want to read settings from, e.g.:

    <uses-permission android:name="android.permission.READ_USER_DICTIONARY"/>
    <queries>
     <!-- To Query Chrome Beta: -->
     <package android:name="com.chrome.beta" />
    
     <!-- To Query Chrome Stable: -->
     <package android:name="com.android.chrome" />
    </queries>
    

    Then, use Android's ContentResolver to request that information by building the content URI as in this example code:

    final String CHROME_CHANNEL_PACKAGE = "com.android.chrome";  // Chrome Stable.
    final String CONTENT_PROVIDER_NAME = ".AutofillThirdPartyModeContentProvider";
    final String THIRD_PARTY_MODE_COLUMN = "autofill_third_party_state";
    final String THIRD_PARTY_MODE_ACTIONS_URI_PATH = "autofill_third_party_mode";
    
    final Uri uri = new Uri.Builder()
                      .scheme(ContentResolver.SCHEME_CONTENT)
                      .authority(CHROME_CHANNEL_PACKAGE + CONTENT_PROVIDER_NAME)
                      .path(THIRD_PARTY_MODE_ACTIONS_URI_PATH)
                      .build();
    
    final Cursor cursor = getContentResolver().query(
                      uri,
                      /*projection=*/new String[] {THIRD_PARTY_MODE_COLUMN},
                      /*selection=*/ null,
                      /*selectionArgs=*/ null,
                      /*sortOrder=*/ null);
    
    cursor.moveToFirst(); // Retrieve the result;
    
    int index = cursor.getColumnIndex(THIRD_PARTY_MODE_COLUMN);
    
    if (0 == cursor.getInt(index)) {
      // 0 means that the third party mode is turned off. Chrome uses its built-in
      // password manager. This is the default for new users.
    } else {
      // 1 means that the third party mode is turned on. Chrome uses forwards all
      // autofill requests to Android Autofill. Users have to opt-in for this.
    }
    

    Deep-link to Chrome settings

    To deep-link to the Chrome settings page where users can enable third-party autofill services, use an Android Intent. Ensure to configure the action and categories exactly as in this example code:

    Intent autofillSettingsIntent = new Intent(Intent.ACTION_APPLICATION_PREFERENCES);
    autofillSettingsIntent.addCategory(Intent.CATEGORY_DEFAULT);
    autofillSettingsIntent.addCategory(Intent.CATEGORY_APP_BROWSER);
    autofillSettingsIntent.addCategory(Intent.CATEGORY_PREFERENCE);
    
    // Invoking the intent with a chooser allows users to select the channel they want to 
    // configure. If only one browser reacts to the intent, the chooser is skipped.
    Intent chooser = Intent.createChooser(autofillSettingsIntent, "Pick Chrome Channel");
    startActivity(chooser);
    
    // If the caller knows which Chrome channel they want to configure, 
    // they can instead add a package hint to the intent, e.g.
    autofillSettingsIntent.setPackage("com.android.chrome");
    startActivity(autofillSettingsInstent);
    

    Updated timeline

    To reflect the feedback and to leave time for autofill service developers to make relevant changes, we are shifting the plan. Users must select Autofill using another service in Chrome settings to ensure their autofill experience is unaffected. The new setting will become available in Chrome 135. Autofill services should encourage their users to toggle the setting, to ensure they have the best autofill experience possible with their service and Chrome on Android. Chrome plans to stop supporting the compatibility mode in summer 2025.

      • March 5th, 2025: Chrome 135 beta is available
      • April 1st, 2025: Chrome 135 is in stable
      • Summer 2025: Compatibility mode will no longer be available on Chrome

    Google Vault now supports the Gemini app

    What’s changing 

    Google Vault now supports the Gemini app (on web and mobile). Going forward, admins can use Vault for eDiscovery tasks to search Gemini app conversations and create an export of your search results. Specifically, the following actions can be taken around Gemini app data: 

    • Search prompts and responses with a number of filters, such as user and date to quickly refine your search. These searches can be across groups of users or by Organizational Units (OUs) up to 5000 in size. 
    • Export conversations in an XML format for the above searches via the UI or API.


    Who’s impacted

    Admins

    Why it’s important

    Vault is an eDiscovery and information governance tool for Google Workspace, which enables customers to retain, hold, search, and export users’ Google Workspace data. With this update, customers can now expand their regulatory and legal eDiscovery needs to include the Gemini app. This integration makes it easier for customers to comply with their eDiscovery obligations surrounding Gemini collaborative data, all from a central tool. 

    Additionally, Vault’s integration with Gemini rounds out support for critical Workspace apps such as Gmail, Drive, Docs, Sheets, Slides, Chat, Calendar and Meet, providing customers with a consistent experience across all products that are managed within Vault for eDiscovery. Additional information governance and hold features, such as preview, retention, and litigation holds will follow in future releases. We’ll share more information on the Workspace updates blog when it’s available.

    Additional details

    This update is not applicable for Gemini for Google Workspace, as no prompts or responses are retained for those interactions. Visit our Privacy Hub for more information on how we’re protecting your Google Workspace data in the era of generative AI.

    Getting started


    Rollout pace


    Availability

    Available to Google Workspace
    • Business Plus
    • Enterprise Essentials and Enterprise Essentials Plus
    • Enterprise Standard and Enterprise Plus
    • Education Standard and Education Plus customers
    • Also available to customers with the Vault add-on license

    Resources

    Easily convert data to people chips and update chip format in Google Sheets

    What’s changing

    Similar to the functionality in Google Sheets that helps you easily convert data to dropdown chips, you can now use bulk chip conversion for people chips. If you have a column of data that includes a variety of emails, Sheets will show a “Convert to people chips” suggestion when you click into your data range. By hovering over that indicator, you can preview the suggestion and then convert your data to people chips in one click. 

    Convert to people chips” suggestion


    In addition to the default format of display name, within the Format menu, you will now be able to update the format of your people chips to one of the following: 
    • Last name, First name 
    • Email address 
    update the format of your people chips


    Getting started 

    • Admins: There is no admin control for this feature. 
    • End users: 
      • To insert people chips on your own, type “@” followed by a name or email address. To change the format of the people chips, select a cell or cells with people chips, go to Format > Smart chips > select the desired format. 
      • To turn off this feature, go to Tools > Suggestion controls > (deselect) Enable dropdown chip suggestions. 
      •  Visit the Help Center to learn more about inserting smart chips in your Google Sheets. 

    Rollout pace 

    People Chip Formats: 

    People Chip Suggestions: 

    Availability 

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

    Resources 

    Meet the Android Studio Team: A Conversation with Director of Product Management, Jamal Eason

    Posted by Ashley Tschudin – Social Media Specialist, MTP at Google

    Dive into the world of Android Studio and meet the masterminds behind your favorite development tools! In our recurring blog series, "Meet the Android Studio Team," we'll introduce you to the brilliant engineers, designers, product managers, and more who are shaping the future of Android development.

    Join us each week to uncover the unique perspectives and stories of the people who make Android Studio the best it can be.


    Jamal Eason: Building better Android apps - insights on Gemini, Crashlytics, and App Quality

    Meet Jamal Eason, a Director of Product Management at Google, whose passion for empowering developers shines through in his work on Android Studio.

    His journey, from studying computer science at West Point to developing Android hardware at Intel (including contributions to the Motorola Razr i), showcases a deep understanding of the developer experience. From attending the very first Android Studio unveiling at Google I/O to now shaping its future, Jamal brings a unique perspective to the team.

    Jamal shares his insights on the evolution of Android Studio, the importance of a strong developer community, and the features he's most proud of.


    Can you tell us about your journey to becoming a part of the Android Studio team? What sparked your interest in Android development?

    I have had an interest in programming at an early age especially since studying computer science in undergrad at the United States Military Academy (West Point), and in that time I have had an interest not just in the creation of software but also in the tools developers use to make software.

    My interest in Android development came when I was preparing for my first job after my telecommunications & computer networks military career when I was joining a team at the Intel Corporation that worked with Google to build Android hardware products. I thought the best way to understand Google and mobile was to download the Android SDK and create my own app end to end. My first taste of Android was Froyo 2.2 using the Eclipse based Android Developer Tools IDE.

    At Intel, I worked on creating the x86 based version of the Android Emulator and Emulator system image, and also a new Hypervisor that would accelerate the performance of the Android Emulator on x86 based laptops. After helping ship the Motorola Razr i (xt890) Android phone with Intel technology inside and x86 optimized apps on the device, I made the move to the Android team at Google. With my experience in developing Android apps, and shipping Android developer tools, the Android developer tools team was a natural fit.

    Interestingly, I attended the Google I/O the year Android Studio was first revealed as an attendee, and the following year I was working on the team to bring Android Studio to its Beta release at the following years Google I/O.

    What unique perspective or experience do you bring to the Android Studio team, and how does it influence your work?

    Unique experiences I bring include:

    • Technical Translation - In my prior roles, I worked with highly technical teams, and learned how to take absurd technical concepts and present them to different audiences of different technical skill levels. And in the reverse, I worked with many non-technical customers and colleagues and learned how to translate their pain points into product opportunities solved with technical solutions and innovation.
    • User Empathy - Previously, I was a software developer, and I regularly like to code on small side projects, and really enjoy spending time with developers who use Android Studio. From first-hand experience and user engagement, I regularly bring in the voice of the user into the discussion from the inception of a product idea to the final stages of the release process.
    • UX Design Sense - In a previous career, I designed and created websites, and user interfaces for software. I developed an eye for good UX design and flows particularly in technical software products. These skills aid in complementing the dedicated UX design team in Android Studio, and aids in avoiding productivity pitfalls with poor product and UX flows.

    In your opinion, what is the most impactful feature or improvement the Android team has introduced in recent years, and why?

    It’s hard to nail down just one, but the top three are:

      1) product quality

      2) integration of Gemini and

      3) integrations with Crashlytics and Play with App Quality Insights.

    The most impactful feature we worked on is product quality. We treat quality, especially the core code editing experience as a feature. If a developer can’t write a line of code and deploy it to a device, then everything else is secondary. Since Android is always evolving, it is an on-going effort but critical for the team to stay focused on.

    On top of quality, thoughtful integration of Gemini into Android Studio is a real accelerate for app development. Our focus with AI is to make Android developers more productive, and make the harder tasks and toil easier. So from AI powered code completion, or built-in Gemini chat for Android app development, to enhancing existing tools with AI such as using Gemini to generate Jetpack Compose UI Previews, we are just at the beginning of leveraging AI to make Android app developers more productive.

    Lastly, with App Quality Insights, it is now much easier for app developers to address the performance and quality issues found with Firebase Crashlytics and Android Vitals from Google Play. Surfacing these issues right next to source code and source control, make resolving issues much faster and intuitive.

    How does the Android Studio team ensure that products or features meet the ever-changing needs of developers?

    First step, the Android Studio team works hand-in-hand with the Android OS team so we strive to deliver developer tools in concert with new Android OS and API changes so developers are ready to adopt new Android platform capability into their apps. Then, we constantly review and prioritize developer feedback received via our issue tracker or via our bi-annaul developer survey we post on the Android Developers site. When we can, we sometimes engage with developers via various social media channels. And lastly, we regularly interview developers at various experience levels, and regions around the world in targeted User Research studies.

    What advice would you give to aspiring Android developers who are just starting their journey?

    1. Start with a robust set of code labs and tutorials.
    2. Get inspired on the possibilities of Android and what you can build.
    3. Join the Android developer community:

    Deploy with Confidence

    Inspired by Jamal's journey and dedication to empowering developers? Explore the latest Android Studio features, including App Quality Insights, to improve your app's performance and address issues quickly.

    Stay tuned

    Don't miss the next installment of our "Meet the Android Studio Team" series, where we'll introduce you to another amazing member of our team and share their unique journey. Stay tuned for more!

    Find Jamal Eason on LinkedIn and X.