Ponny
#1
Logged in today after noticing some access errors. I log in to the dev portal and see " Last generated: Aug 28, 2020" on our “Access token & access token secret” section. Is this something that Twitter is automatically doing? We definitely did not regenerate it.
Strangely, login was still working but our consumer keys stopped working. I regenerated our consumer keys but they still won’t work. Our app ID is 4206775, if that helps. Will I have to regenerate the whole lot again for them to start working?
This is under my personal account. Nobody else has access to it (strong, unique password and 2FA too) and there are no other active team members.
UPDATE: Despite it being generated so recently, tokens from before 28th august (we checked one from 20 aug) are still working fine. Perhaps this date is a display bug on the UI?
UPDATE 2: We’ve regenerated our consumer API keys but they always receive a ‘{“errors”:[{“code”:89,“message”:“Invalid or expired token.”}]}’. Any ideas why this would no longer work?
UPDATE 3: FYI It IS the 28th here in Australia even though I was posting this on the 27th US time. I’m guessing/hoping that the UI there is in my time zone and not in the future?
UPDATE 4: Regenerated our “Access token & access token secret” and now everything’s working fine again. Still don’t know how they got regenerated earlier “today” so I’d really apprecaite any information the Twitter team could provide.
Everything on twitter API should be in UTC time - but maybe the web interface was using local time or something? Maybe that was it?
1 Like
system
Closed
#3
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
