-
Notifications
You must be signed in to change notification settings - Fork 38
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
Fixed: Error 403 on person #181
Comments
Hi, It was reported on hacf-fr/hassRenaultZE#120, but I don't have a root cause for it yet. Also, it affects all endpoints, not just |
According to @dehsgr is a new Kamereon API key needed: Ae9FDWugRxZQAGm3Sxgk7uJn6Q4CGEA2 |
PR works for me too, thanks! |
Before I merge, I would like to know how to make it work for @db-EV |
It's working for me now as well. You can go ahead. |
When I decompiled the app it still has the old values in it. So I am quite sure they deploy the new values using Firebase remote-config: https://firebase.google.com/docs/remote-config A test to check this would be to install the official app on an android device without Google Play Services (e.g. a LineageOS custom ROM and not installing any GApps) and to see if the app gets the updated key or not (I suspect not: because Firebase depends on Google Play Services). Afaik there is no method (yet) to eavesdrop on the Firebase/Google connection. Though you could try to check the contents of the local configuration SQLite database of the app. |
Yes, I was able to retrieve a sample from Firebase here: #184 |
Is anyone experiencing error 403 ?
Today I'm getting this error:
aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url=URL('https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/persons/86523cf5-aa91-4bfd-b76e-0f744e1ccf31?country=IT')
Thank youRoberto
The text was updated successfully, but these errors were encountered: