Pleroma Refresh Token doesn't set the new bearer token

[absturztau-be]

The Bearer Token doesn't get properly set when the app refreshes the token leading to notifications, bookmarks and other stuff that require authentication not loading.
If i set the new bearer token manually in localStorage.multi[target].at through the console, it works

To Reproduce
Steps to reproduce the behavior:

1. Authenticate a Pleroma Account
2. When the Columns view gets displayed, the app refreshes the token but still uses the bearer token it got from the first time
3. Add Notifications or Bookmarks column, it wont display anything in those columns.
4. The requests to the api endpoints return 403

Expected behavior
after refreshPleromaAt() is run, the new access token should be set in localStorage.multi[target].at so every request from that point on will use the newly received token instead of the first (now invalid) one

Environment

• OS: Linux Manjaro
• Version: 22.1.0 (Koume) 7f79f17
• Your instance: fedi.absturztau.be