[@nativescript/google-maps] New Android Google Maps SDK renderer

Hi, Google is asking developers to update to the new Android Google Maps SDK renderer. I would like to be sure that my apps won't be affected by this change while in production.

From what I've read, no action is required if the app and plugin use Maps SDK for Android v. 18.2.0 and do not specify a renderer.

Does @nativescript/google-maps meet these criteria?

This is the email sent by Google:

You may have projects using the legacy renderer that will be decommissioned by March 3, 2025. Apps built with the Maps SDK for Android will be automatically updated to the latest renderer beginning March 4, 2024.

Hello Google Maps Platform Customer,

This is a follow up to the announcements sent in 2021 and 2022 regarding the new renderer for Maps SDK for Android. To provide an improved user experience and app performance, apps built with the Maps SDK for Android will be automatically updated to the latest renderer beginning March 4, 2024. The legacy renderer is scheduled for decommissioning on March 3, 2025.

What do I need to know?

The new renderer was introduced in Maps SDK for Android version 18.0 in an opt-in manner. It is offered as a default starting on version 18.2, with an option to specify the Legacy renderer (Renderer.LEGACY).

Your app may be currently using the legacy renderer in two situations.

Situation 1.If you use Maps SDK for Android version < 18, or 18.0-18.1 without opting in the new renderer:
The automatic update to the latest renderer will be rolled out to the Android devices in a gradual ramp up mode and is expected to impact 100% of all supported devices by the end of 2024.
Situation 2. If you specify the legacy renderer (on version 18.0 or later):
Your application will continue receiving the legacy renderer until March 2025. Starting in March 2025, you will get the new renderer even if you specify the Legacy renderer.
During the migration period, Google will continue to provide support and fixes to major bugs and outages on the legacy renderer. New features and improvements are only offered on the new renderer.

The new renderer is currently only available on Android phones. If your app is used on Wear OS or Android Go, the new renderer will be available in Google Play Services at a later time. Please follow the progress on this rollout by starring this issue tracker entry.

What do I need to do?

No action is recommended if your app already uses Maps SDK for Android v18.2.0 and does not specify a renderer during the initialization process.

Updating to the latest renderer in the Maps SDK for Android may introduce a slight change to the performance and behavior of the maps in your app. Google does not expect this to cause any operational issues.

We recommend that developers of mission-critical apps test their application with the new renderer ahead of the automatic update (happening in March 2024 or March 2025 depending on your situation above), in order to limit risks of potential issues. You can do this by updating the dependencies for your app to the Maps SDK for Android version 18.2.0 or later, without specifying the Legacy renderer (Renderer.LEGACY).

See release notes for differences between older versions and version 18.2.0.

Inspectez la dépendance Android @nativescript/google-maps et l’initialisation de la carte afin de déterminer quelle version de Maps SDK est utilisée et si un renderer est spécifié. Le travail est considéré comme terminé lorsque vous avez documenté si le plugin respecte les critères de Google concernant v18.2.0 et le renderer, ainsi que toute action requise.