#rakesh-m-r_code

1 messages ¡ Page 1 of 1 (latest)

hasty pagodaBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1357630263399546880

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

undone sentinel
#

hi there!

#

what's your question/issue?

swift crow
#

we want get rid of these warning

#

in console

undone sentinel
#

which warnings? can you clearly explain/summarize your issue here?

swift crow
#

As of March 1st, 2025, google.maps.places.PlacesService is not available to new customers. Please use google.maps.places.Place instead. At this time, google.maps.places.PlacesService is not scheduled to be discontinued, but google.maps.places.Place is recommended over google.maps.places.PlacesService. While google.maps.places.PlacesService will continue to receive bug fixes for any major regressions, existing bugs in google.maps.places.PlacesService will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/legacy for additional details and https://developers.google.com/maps/documentation/javascript/places-migration-overview for the migration guide.

we are getting above warning in console when using AddressElement

undone sentinel
#

got it. if it's just a warning, it shouln't have any impact on the Addresselement itself.

#

and I don't think there's a wayt o remove that warning on your end

swift crow
#

okk so this should be fixed in upcoming versions?

undone sentinel
#

we regularly make updates to improve our apis, so yes you can expect that this will be fixed at some point.