Activity log for bug #1387829

Date Who What changed Old value New value Message
2014-10-30 18:28:08 Chris Wayne bug added bug
2014-10-30 18:28:15 Chris Wayne go-onlineaccounts: status New Confirmed
2014-10-30 18:38:39 Chris Wayne description Until the watcher.Wait() is ready to use, I basically setup a counter in my scope to check for an access token, and wait 100ms and try again if none is found. I've seen this iterate 60 times and still not find an account even though there is an account present. In some go scopes, the scope cannot get the access token to an authenticated account even after 6 seconds of trying. This results in no data being shown, and a "Please setup an account" result being shown, even though there is an account setup, which is of course a horrible user experience. Prior to watcher.Wait(), I had setup a system to try to get the access token from AuthData, then sleep 100ms and retry if none was receieved. I've seen this run 60 times without receiving the AccessToken from the channel. Is there either a better way to do this from within the scope, or is this an issue with signond itself, or the bindings?
2014-10-31 10:15:57 Joe Odukoya tags rtm14
2014-10-31 11:02:41 Alexander Sack go-onlineaccounts: importance Undecided Critical
2014-10-31 11:08:04 Alexander Sack summary Takes too long (sometimes over 5 seconds) to get the AccessToken from watcher.C [TOPBLOCKER] Takes too long (sometimes over 5 seconds) to get the AccessToken from watcher.C
2014-10-31 14:55:58 Chris Wayne go-onlineaccounts: status Confirmed Fix Committed