status-im
/
status-go
mirror of https://github.com/status-im/status-go.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-go/mobile
History
Icaro Motta 14c996158c
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

---------

Co-authored-by: Igor Sirotin <sirotin@status.im>
 		2024-08-26 10:56:39 -03:00
..
README.md rename status-react to status-mobile 2022-07-17 15:37:14 +02:00
multiaccount.go feat: create acc from private key endpoint added 2023-03-28 16:19:27 +02:00
response.go Use eth-node `keystore` for `generator.go` 2020-01-06 15:45:31 +01:00
response_test.go converting desktop key to mobile readable (#3042) 2023-01-04 07:25:07 +05:30
status.go feat(accounts)_: Persist acceptance of Terms of Use & Privacy policy (#5766) 2024-08-26 10:56:39 -03:00
status_geth.go remove nimbus 2021-05-21 07:22:58 +02:00
types.go Return keyUID on succesfull validation of mnemonic 2023-03-28 10:52:06 +02:00

README.md

Mobile

Package mobile implements gomobile bindings for status-go. Current implementation servers as a drop-in replacement for lib package.

Individual bindings and their descriptions are available in status.go.

The primary consumer of this package is status-mobile project.

The framework name is generated from the package name, hence these things are done intentionally: (1) this package's name isn't equal to the directory name (statusgo vs mobile respectively); (2) this package name is statusgo and not status which produces the right framework name.

Usage

For properly using this package, please refer to Makefile in the root of status-go directory.

To manually build library, run following commands:

iOS

gomobile bind -v -target=ios -ldflags="-s -w" github.com/status-im/status-go/mobile

This will produce Statusgo.framework file in the current directory, which can be used in iOS project.

Android

gomobile bind -v -target=android -ldflags="-s -w" github.com/status-im/status-go/mobile

This will generate Statusgo.aar file in the current dir.

Notes

See https://github.com/golang/go/wiki/Mobile for more information on gomobile usage.