-
Notifications
You must be signed in to change notification settings - Fork 17
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
BlahBlah?? #35
Comments
Same thing here; my guess: someone @ Nissan (or more likely, a subcontractor) deployed in PROD some debugging code. |
Seeing the same, and chuckled. A small part of me wonders if there is a new or different API endpoint (?) for auth since the Nissan EV&Services app connects and is still working right now with my US 2017 LEAF. Their app actually seemed speedier than average, and it seems to actually be working at the moment, so that much is hard to complain about. It is definitely a strange response from an API call for sure, and not very professional. :D Hopefully they figure it out. |
I am seeing something similar: |
Are you using https://gdcportalgw.its-mo.com/api_v210707_NE/gdc/? If not try it, the older ones just expired and gave me the same error. |
The US API endpoint seems to have changed, likely with the advent of the pending Ariya release. From:
To:
|
Looks like the API key sent in headers changed too, because just using that new URL fails with an |
Was able to see the new URL and API key by using Charles Debugging Proxy on an iOS device. (It doesn't work on Android anymore, since Android N.) |
Merci énormément!!!! :) |
Your suggestion worked, just changing the baseURL worked to fix my issue. |
Oh no, it's is starting again with the new link: |
Since Sept 9, I get a Non-JSON response: BlahBlah! This is very weird. Any other have the issue? Maybe the URL have changed? On Nissan got hacked? Lol
The text was updated successfully, but these errors were encountered: