Write authentication issue causes flagging via FIRE to fail

[bertiebaggio]

I have been using FIRE to provide feedback to MS, and where relevant, submit flags on posts that are still alive. Sometime since the first week of December 2018 (or so), my flags have not been going through; and FIRE is instead showing me a notification window that I need to be write-authenticated.

The link in the dialog takes me to the authentication status page (https://metasmoke.erwaysoftware.com/authentication/status) on MS, which tells me:

Authenticate with Stack Exchange

Associate your metasmoke account with your Stack Exchange account to provide feedback through the API.
(you have already authenticated)

Clicking the button to reauthenticate gives me a 'success' result but does not change the behaviour of FIRE.

The application 'metasmoke' appears in the list of authorised apps on my SE profile.

For completeness, using the 'reinstall' button on the FIRE userscript hasn't changed anything, though 1)
FIRE uses localStorage which persists across reinstalls and 2) this is "100% an MS issue" !

I am happy to reinstall / reauth / run stuff as needed to help ping down the issue.

---

From: Why can't I flag? FIRE keeps telling me I need to be write-authenticated on Teams

[thesecretmaster]

Looks like all of authentication_controller & helper didn't get updated for the new token store.

[bertiebaggio]

I can confirm this is now solved due to changes made as of 0fa8f5a

Thanks to @thesecretmaster and others involved in the process