132ea05fc8
* feat(accounts)_: Persist acceptance of Terms of Use & Privacy policy (#5766) 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 * fix(test)_: Compare addresses using uppercased strings --------- Co-authored-by: Icaro Motta <icaro.ldm@gmail.com> |
||
|---|---|---|
| .. | ||
| 0001_accounts.down.sql | ||
| 0001_accounts.up.sql | ||
| 1605007189_identity_images.down.sql | ||
| 1605007189_identity_images.up.sql | ||
| 1606224181_drop_photo_path_from_accounts.down.sql | ||
| 1606224181_drop_photo_path_from_accounts.up.sql | ||
| 1648646095_image_clock.down.sql | ||
| 1648646095_image_clock.up.sql | ||
| 1649317600_add_color_hash.up.sql | ||
| 1660238799_accounts_kdf.up.sql | ||
| 1679505708_add_customization_color.up.sql | ||
| 1687853321_add_customization_color_updated_at.up.sql | ||
| 1719915420_add_appmetrics.up.sql | ||
| 1724407149_add_has_accepted_terms_to_accounts.up.sql | ||
| doc.go | ||