14c996158c
The original GH issue https://github.com/status-im/status-mobile/issues/21113 came from a request from the Legal team. We must show to Status v1 users the new terms (Terms of Use & Privacy Policy) right after they upgrade to Status v2 from the stores. The solution we use is to create a flag in the accounts table, named hasAcceptedTerms. The flag will be set to true on the first account ever created in v2 and we provide a native call in mobile/status.go#AcceptTerms, which allows the client to persist the user's choice in case they are upgrading (from v1 -> v2, or from a v2 older than this PR). This solution is not the best because we should store the setting in a separate table, not in the accounts table. Related Mobile PR https://github.com/status-im/status-mobile/pull/21124 --------- Co-authored-by: Igor Sirotin <sirotin@status.im> |
||
|---|---|---|
| .. | ||
| accounts | ||
| common | ||
| errors | ||
| migrations | ||
| settings | ||
| settings_notifications | ||
| settings_wallet | ||
| database.go | ||
| database_test.go | ||