I am having this issue that Will was having with the "isn't in the correct format" error. Is this fixed, and/or where can I modify the code? I can tell you my password does not have those symbols at this time.Well, if you want your symbols back (and for the others still having issues and also have ants in their pants waiting until @tonesto7 puts this into an upcoming version), replace line 1152 from the 1.1.1 version of the script with this:
req.body = encodeURI(`client_id=9fb503e0-715b-47e8-adfd-ad4b7770f73b&grant_type=password&username=${username}&password=${password}`);
and you should be all good.
This script stopped working for me too a while ago. The last I heard, Ford shut us out, and there was word Ford might be offering a new, authorized way to get the data. I haven’t heard any updates about that in months, though.I am having this issue that Will was having with the "isn't in the correct format" error. Is this fixed, and/or where can I modify the code? I can tell you my password does not have those symbols at this time.
I think the overarching issue is Ford is actively subverting the efforts of the people like @tonesto7 by changing the API regularly.I stumbled on this thread just in the past day or so. Given the changing API issues, does it make sense for someone (me) to start this process from scratch? Sounds like the overall script doesn’t currently function?