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

open_now and utc_offset is deprecated #3404

Open
ikarofelix opened this issue Feb 1, 2025 · 0 comments
Open

open_now and utc_offset is deprecated #3404

ikarofelix opened this issue Feb 1, 2025 · 0 comments

Comments

@ikarofelix
Copy link

Everything I find about this issue is pretty old, and some even mentioned updating the library. I'm using the latest version, and this issue disappeared for a few days, but now it's back.

Error:
More than 190 errors mentioning utc_offset or open_now.

Image

Image

Application flow:

First, I call getPlaceDetails to retrieve the name, address, etc.:

Image

I'm destructuring everything to make sure I'm not receiving anything related to utc_offset or isOpen, but from the console log, I can see that I'm not receiving those fields since they are not included in fields.

Here's the console log of the place:

Image

After that, formData simply structures the place information, and then I call handleNearbyPlaces. This NearbyPlaces function tries to find, for example, restaurants near the place's latitude and longitude.

Image

This nearbyPlaces request allows passing openNow: true, but whether I pass true or false, the error persists.

In other words, nowhere in my code do I request open_now or utc_offset, yet I'm still getting the error.

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

1 participant