- Posted on
Mon Aug 20, 2018 1:09 pm
-
colovin
offline
-
- Posts: 173
- Joined: Oct 27, 2009
I had done a search for Callback URL before posting this which maybe I was searching in the wrong place because it came up with nothing. Found something on page 3 of the sticky which addressed the issue. My scope was approved I clicked on the approved box which brought me to the call back page which I screwed up the first time through. Once I understood what was going on I hit the click to authorize again, copied and pasted the callback URL, clicked the obtain access token which it came back as successful. In setting up the device , in the setup screen the Vehicle screen is ghosted with no items to select. Did I screw the pooch when I screwed up the Callback URL on the first go around? Here's what's going on in the log.
Automatic OBD-II {"access_token":"f8c3dfba20f6dbd08b881b4d430876644xxxxxxx”,”scope":"scope:behavior scope:location scope:offline scope:public scope:realtime:location scope:trip scope:user:profile scope:vehicle:events scope:vehicle:profile","expires_in":2591xxx,"refresh_token":"4d329e269883c8b8499178bf61b181601xxxxxxx","token_type":"bearer","user":{"id":"U_4d68cb96exxxxxxx”,”sid":"U_4d68cb96exxxxxxx”},”user_id":"U_4d68cb96exxxxxxx”}
Automatic OBD-II f8c3dfba20f6dbd08b881b4d430876644xxxxxxx
Aug 20, 2018, 11:35:47 AM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'id'
Indigo 7.1.1, OS 10.14.6, MacMini .3.2 GHz 6 Intel Core i7, 64 GB ram