Thursday, December 2, 2021

Latest version of Chrome requires extra step to get Mint authentication info

Hi All,

It appears that Chrome moved the "Form Data" section to a separate tab within the DevTools / Network window. You now have to copy the data from the "Headers" tab (to get the cookies) and the "Payload" tab (to get the token).

14 comments:

  1. Thank you so much! I was wondering. I had a computer with a non updated version of Vivaldi and it worked. I will send an donation for your attention to this. Thank you!

    ReplyDelete
  2. Brian,

    It looks like Mint changed their page, and the track.xevent is gone now... Are we done? Will we be able to keep using this?

    Thanks
    Joshua

    ReplyDelete
    Replies
    1. Hi Joshua,
      I just tried it and it worked fine for me. Make sure you are navigating to the OVERVIEW tab in Mint. Also, sometimes the track.xevent request isn't sent (the data is probably cached in the browser), so you have to force-refresh the OVERVIERW page (Shift+F5 on Windows). However, it's possible that Mint is rolling out some changes that haven't been applied to my account yet. Maybe it will stop working for me soon, too. (Hope not)

      Delete
  3. This comment has been removed by the author.

    ReplyDelete
  4. I'm looking for track.xevent and I'm not finding it now. Has anyone been able to connect up since the new UI update from Mint.com? Ohhhh boy taxes are going to be unbelievable difficult to file this year without this.

    ReplyDelete
    Replies
    1. @b3devs Hopefully, this is still working.

      Delete
    2. I am still seeing the track.xevent request, but maybe I haven't gotten the new UI update yet?? Here are the notes I sent to another Mojito user (above, on March 8, 2022):
      Make sure you are navigating to the OVERVIEW tab in Mint. Also, sometimes the track.xevent request isn't sent (the data is probably cached in the browser), so you have to force-refresh the OVERVIERW page (Shift+F5 on Windows).

      Delete
    3. When you have the new ui you'll know it. The new ui is very different. It's my understanding it is beta for some people and they can choose not to migrate to the new version.

      Delete
  5. I haven't been able to sync my Mint account since February. the Payload workaround worked at the beginning, but now I'm getting "Assertion Error
    splitCount === result.responseJson.txnId.length - 1"

    I have not changed my excel spreadsheet.. How can I fix it?

    ReplyDelete
  6. FYI – I checked in with mint.com technical support, and they said there is no way to toggle between the new view and old view (I remember gmail provided that as an option for what seemed to be years!). Also, while there are still migrations happening, they had no idea how to “force” an upgrade for those that are not currently migrated, nor know when all of the migrations will be completed.

    ReplyDelete
  7. same as others - no track.xevent

    ReplyDelete
  8. Any updates on this? I can't sync either. The track.xevent doesn't work even if I refresh a few times. Thanks for any insights!!

    ReplyDelete
  9. I have no way to connect. Have not used mojito for three months, now there is no answer with track.xevent nor bundledServiceController.xevent

    ReplyDelete
  10. Hi folks. Mojito is broken and won't be fixed until I am able to update it to work with the Mint UI (not trivial). I posted a note about the situation today. https://b3devs.blogspot.com/2022/07/mojito-is-broken-due-to-mint-ui-overhaul.html

    ReplyDelete