-
Notifications
You must be signed in to change notification settings - Fork 634
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
Error: paramsSerializer is not a function #991
Comments
If you would like to upvote the priority of this issue, please comment below or react with 👍 so we can see what is popular when we triage.@exipnus Thank you for opening this issue. 🙏
This is an automated message, feel free to ignore. |
also running into this issue intermittently but infrequently when hitting |
Just wanted to say that I'm also running into this very very intermittently. We're sending a few million API calls a month, and over the past 30 days have seen this 27 times, 8 times today specifically A sample request that failed:
|
Hello, Any news on this? Thank you |
I am experiencing this with all of my requests today. |
I suddenly have this issue, without making updates or any changes. |
I tried it again with my mobile hotspot instead of wify and now it works. Does anybody understand what's happening? This is the srangest issue I've ever had. Since the error says that paramsSerializer is not a function, it seems code related, but simply changing the network solves the issue? Also, I've tried some direct API calls (without the client) with the same API key in my wifi network (where I receive the error), where it works smoothly, so it cannot be related to my IP address being blocked or something. I don't get it. If anybody has ideas, please let us know. Thank you! #Edit: After Network Switch back to wifiy it seems to work again, while 100% of all requests failed before. |
Just wanted to add to this. We've noticed this error occurring with other endpoints, like reverse geocode and find place |
I've also been getting this irregularly with the |
Can you check with the latest version (we just recently upgraded axios to v1.5) if that problem still occurs? |
For us, it was actually a network error. We had been getting random network errors ever since we upgraded from Node v18 to Node v20, upgrading to Node v20.5 magically fixed these network errors. (This is the issue if someone would like to read more nodejs/node#47822) I think the main problem here is figuring out why the library is reporting network errors as |
That just got me thinking, it could be that this is somehow related to the |
In case if it helps anyone facing this issue. We recently upgraded to Seems like the issue got fixed by the upgrade of |
I'll close this for now. Please reopen or create a new issue if you are still seeing this problem. |
API: Places Autocomplete
OS: Ubuntu with WSL 2 (Windows 11)
Platform: next.js with Typescript
Library version: 3.3.31
I have also tried:
the error I get is:
Any ideas?
The text was updated successfully, but these errors were encountered: