Migrate to GMA Next-Gen SDK

[mmathieum]

https://developers.google.com/admob/android/next-gen/migration

[gemini-code-assist]

Summary of Changes

Hello @mmathieum, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request initiates the migration to the Google Mobile Ads Next-Gen SDK. The core changes involve updating the ad dependency to the new module and version, alongside implementing specific exclusion rules to manage potential conflicts with older ad service libraries. This ensures the application leverages the latest advertising platform features and improvements, streamlining the integration process for future ad-related functionalities.

Highlights

• GMA Next-Gen SDK Migration: The project has been updated to migrate to the Google Mobile Ads (GMA) Next-Gen SDK, as indicated by the changes in dependency versions and module names.
• Dependency Updates: The gps-ads dependency version has been updated to 0.24.0-beta01 and its module path changed from com.google.android.gms:play-services-ads to com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk.
• Dependency Exclusions: Exclusion rules have been added in the main application's build.gradle to prevent conflicts by excluding play-services-ads and play-services-ads-lite from configurations when isMainApp is true.

Changelog

• gradle/libs.versions.toml
  • Updated the gps-ads version from 25.0.0 to 0.24.0-beta01.
  • Changed the gps-ads module from com.google.android.gms:play-services-ads to com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk.
• shared/app-android/build.gradle
  • Added a conditional block to exclude com.google.android.gms:play-services-ads and com.google.android.gms:play-services-ads-lite from all configurations when isMainApp is true.

Activity

• No specific activity (comments, reviews, progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request successfully migrates the project to the GMA Next-Gen SDK by updating the gps-ads version and module in gradle/libs.versions.toml and adding exclusion rules for the old play-services-ads dependencies in shared/app-android/build.gradle. The changes appear to align with the migration guide provided in the PR description. The exclusion rules are a good practice to prevent conflicts with the new SDK.