Bug #2121

Pasting new token does not make account active

Added by Panagiotis Louridas about 12 years ago. Updated almost 12 years ago.

Status:Closed Start date:03/01/2012
Priority:High Due date:
Assignee:Panagiotis Kanavos % Done:


Category:Taskbar app Spent time: -
Target version:PreAlpha


After my token had been changed on the server, the client correctly detected that and made the account inactive. I saw the related message and went to the Preferences where I copied and pasted the new token. However, the account was not made active. The only way I could find for that was to click on refresh, so that in essence I got yet another token.


#1 Updated by Panagiotis Kanavos about 12 years ago

  • Category set to Taskbar app
  • Status changed from New to Resolved
  • Assignee set to Panagiotis Kanavos
  • Target version set to PreAlpha

The Shell.MonitorAccount method was not passing the changed properties to the PithosMonitor class which is responsible for monitoring each separate account.

The Refresh button will attempt to retrieve the valid token from the server. It will not try to renew the token. It is the preferred way to refresh the token for an expired account.

The Refresh method was updating the PithosMonitor class before calling Shell.MonitorAccount

#2 Updated by Panagiotis Kanavos about 12 years ago

  • Status changed from Resolved to Feedback

#3 Updated by Panagiotis Kanavos almost 12 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF