Hotfix to correct gaiaHubConfig info in profile.json

[hstove]

No description provided.

[kantai]

Can you add a state change version bump to force a rewrite?

[hstove]

The way the state update logic works is that it updates the profile.json for all local identities you have in the browser. This should be sufficient, because the only effected profile.json's are the ones you've logged into with in your browser.

It iterates and updates all profile.json's before even updating state.

When updating the profile.json, it creates a new Gaia token before signing, so any effected Gaia tokens in the profile.json will not be used. This means they can be invalidated before doing the state update, and the write will still work.

[kantai]

When updating the profile.json, it creates a new Gaia token before signing, so any effected Gaia tokens in the profile.json will not be used. This means they can be invalidated before doing the state update, and the write will still work.

Yep -- can confirm that this is the case: the uploadProfile function here https://github.com/blockstack/blockstack-browser/blob/f2b12bf51123a696ef64fd65c730ebe050e04eb2/app/js/account/utils/index.js#L84
always tries to generate a new token on the fly, anyways.

[kantai]

This worked for me as well, @hstove

[yknl]

This works well for me.

[hstove]

Thanks for the reviews. I also removed the calls to add browserVersion in the gaia token payload, as it's no longer necessary.