Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Maps SDK renderer compatibility #2888

Closed
3 tasks
alexp25 opened this issue Oct 27, 2021 · 8 comments
Closed
3 tasks

New Maps SDK renderer compatibility #2888

alexp25 opened this issue Oct 27, 2021 · 8 comments

Comments

@alexp25
Copy link

alexp25 commented Oct 27, 2021

I'm submitting a ... (check one with "x")

  • [ x ] question
  • any problem or bug report

OS: (check one with "x")

  • [ x ] Android
  • iOS
  • Browser

Google has issued a warning that a new renderer will start to roll out next year:

https://developers.google.com/maps/documentation/android-sdk/renderer

Here is some info received by email from Google:

"This Maps SDK update features a new map renderer, which will become the default renderer for Android devices* through a progressive rollout, starting in March 2022 at the earliest.

Update to the new SDK (version 18.0.0) now to test and deploy the new SDK and renderer with your apps before the new renderer becomes the default for Android devices*.

To anticipate and avoid issues with your apps we advise you to:

  1. Use the new SDK.
  2. Specify the new renderer in your code."

What is to be done? Will the new renderer break everything, or how should we proceed to ensure a smooth transition?
It looks like there are just a few updates required (see link above).

@alexp25
Copy link
Author

alexp25 commented Nov 29, 2021

I think a better question would be if it's really required to use the new renderer once it's rolled out. It says "An upgraded map renderer is available as of version 18.0.0 of the Maps SDK for Android". Does this mean that the new renderer only applies when using com.google.android.gms:play-services-maps:18.0.0? The plugin uses version 16.0.0 by default, which means it's not affected and should continue to work (please confirm, I am not really sure about that)

@xinfengmich
Copy link

I have the same question. Will this plugin have a new release to use com.google.android.gms:play-services-maps:18.0.0 soon? Or any option to set using com.google.android.gms:play-services-maps:18.0.0?

@alexp25
Copy link
Author

alexp25 commented Feb 18, 2022

There is an additional message from Google which enforces the previous concerns regarding the compatibility risk: Once the new renderer becomes the default, your apps will use the new renderer whether or not they were built against Maps SDK for Android version 18.0.x.
At least the deadline was pushed to starting in June 2022 at the earliest, so there is still time to make the required changes.

@EinfachHans
Copy link
Contributor

I just forked this Plugin because i guess no more work is done here...

See how easy it is to use the new renderer: https://github.com/EinfachHans/cordova-plugin-googlemaps/commit/71d8d45286a451270518847f95a25e74ee7fa382

@alexp25
Copy link
Author

alexp25 commented Feb 19, 2022

@EinfachHans great job! It works like a charm, my app seems to be using the latest renderer with no problems so far

@uhmarc
Copy link

uhmarc commented Apr 30, 2022

@EinfachHans Is your fork working with Android 10? Specifically this issue here:
#2892

@EinfachHans
Copy link
Contributor

@uhmarc i target sdk 30 so yes

@uhmarc
Copy link

uhmarc commented May 1, 2022

@uhmarc i target sdk 30 so yes

Thanks, will be using it! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants