Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't lose map options when upgrading or codepush-ing #4849

Open
bengtan opened this issue Feb 28, 2020 · 4 comments
Open

Don't lose map options when upgrading or codepush-ing #4849

bengtan opened this issue Feb 28, 2020 · 4 comments
Assignees

Comments

@bengtan
Copy link
Contributor

bengtan commented Feb 28, 2020

From https://github.com/hippware/collaboration/issues/22#issuecomment-586364539:

User has the map orientation set to satellite, the user updates the app and the orientation has now reverted back to the default.

I believe this is referring to the mapOptions setting in HomeStore. It's lost upon upgrade (or codepush). It'd be nice to preserve it across upgrade or codepush.

@aksonov aksonov self-assigned this Mar 4, 2020
@southerneer
Copy link
Contributor

Whatever solution we come up with should be capable of generalizing to other pieces of local state that we want to survive across upgrades/codepushes since this kind of request will inevitably come up again.

@bengtan
Copy link
Contributor Author

bengtan commented Mar 5, 2020

Here's some past history that's probably relevant.

There was a ticket ...

... which had a similar problem.

There was a discussion ...

... on how to fix it.

There was some talk about (creating and) preserving a dedicated part (ie. 'settingsStore'?) of the MST tree across upgrades. But this was short-circuited by just storing in clientData instead.

So, for this ticket, I guess we could revive the discussion about 'settingsStore' or just store it in clientData.

aksonov added a commit that referenced this issue Mar 5, 2020
@aksonov
Copy link
Contributor

aksonov commented Mar 5, 2020

@bengtan Yes, I solved it in the same way as I did with 'invisible' mode before.

southerneer added a commit that referenced this issue Mar 5, 2020
@bengtan
Copy link
Contributor Author

bengtan commented Mar 9, 2020

QA notes:

This ticket should be tested by upgrading from a version which already includes this ticket.

This was referenced Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants