You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading from "@googlemaps/google-maps-services-js": "3.1.16" -> "@googlemaps/google-maps-services-js": "3.2.0" started getting this error:
Using "react-native": "0.65.1".
Tried this, but it didn't help, other solutions involve deprecated packages and for that reason, I won't try them, for now downgrading to 3.1.16 works just fine for me.
The text was updated successfully, but these errors were encountered:
Darapsas
added
triage me
I really want to be triaged.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
labels
Sep 22, 2021
Tried 3.2.2 today, but no luck:
Looking a bit deeper, the crypto package is empty with a deprecation warning:
Tried rn-nodeify workaround with the latest 3.2.2, seems to be working (didn't test it that much, but at least the application starts without errors). Of course, this is a very hacky way, I will try to look for a cleaner solution if it exists, but it will suffice for now.
It would be really cool to see this package use crypto-js instead of the core node module - crypto, for all the people who use google-maps-services-js with client applications (like react-native or other web-applications). All things considered I am pretty sure this is not going to happen, but at least you could add this workaround to the documentation for others to see.
After upgrading from
"@googlemaps/google-maps-services-js": "3.1.16"
->"@googlemaps/google-maps-services-js": "3.2.0"
started getting this error:Using
"react-native": "0.65.1"
.Tried this, but it didn't help, other solutions involve deprecated packages and for that reason, I won't try them, for now downgrading to
3.1.16
works just fine for me.The text was updated successfully, but these errors were encountered: