Have the exact same problem like bitAndy. Toggling time from auto to manual did not work.
Good to know that you made a bug report.
Have to wait but it's OK
Obits, Metafees hey hey
Fix real quick so I can buy
The assets which go to the sky
Maybe it is a time zone problem. The server is in GMT+5 (Eastern Standard Time), you can put your clock to EST.
Here is what has been done so far.... One of the tests is this: test in FF and Chrome by moving my timezone across the world. The new time did show up in JavaScript but yet I was able to get the claim through ( it did not expire ). Details below..
Some changes were made ( on good direction from DL ). This change was committed on Oct 5th:
// With a lot of balance claims the signing can take so Long
// the transaction will expire. This will increase the timeout...
tr.set_expire_seconds(config.expire_in_secs + balance_claims.length)
One second per signature is probably 10 to 50 times longer that we need, I did check this at the time. The config.expire_in_sec is only 15 seconds, this is done on purpose to keep the UI and the blockchain state consistent ( more on that below ).
Also, if you have many balance claim entries you will see multiple lines in the UI so you can check off and claim them separately. This will group balance claims in the UI by groups of 60:
// Signing is very slow, further divide the groups based on the number of signatures required
var batch_number = Math.ceil( groupCount(Immutable.List([names, v.balance.asset_id]), v.owner) / 60 )
The expiration is based off of this time ( open the wallet and this will run in the browser's console ):
ChainStore.getHeadBlockDate().toISOString()
The ISO date string returned above should show an accurate Zulu time regardless of you local clock time and regardless of your timezone. Google printed the current Zulu time when I queried for it:
https://www.google.com/?q=zulu%20time .. Also ChainStore.getHeadBlockDate().getTime() will be very stable too (other than milliseconds that go by between the timezone change). Finally, I verify that the timezone change is seen immediately in the browser by running: new Date().toString()
If it is expiring, how many seconds pass after you click "Confirm" on the transaction confirm dialog? Are these issues related to older versions of the browser?