We now check that we are only connected to some `peers` instead of using `NetInfo` from `react-native`.
This is because it has been reported to be quite flaky at times, not reporting online status after sleeping, and for privacy concerns (on ios it pings `apple.com`, on desktop `google.com`).
Adds a new banner `Wallet Offline` and change `Connecting to peers` to `Chat offline`.
A message will be marked as `Sent` only if it made it to the mailserver you are connected to, which will increase the guarantees that we can make about a message (if you see it as sent, it has reached at least a mailserver), this has the consequence that:
- If you are not connected to any mailserver or the mailserver is non responsive/down, and you send a message, it will be marked as `Not sent`, although it might have been actually made it in the network.
Probably this is something that we would like to communicate to the user through UX (i.e. tick if made it to at least a peer, double tick if it made to a mailserver )
Currently I have only enabled this feature in nightlies & devs, I would give it a run and see how we feel about it.
Adds a `chat-id` field in `content` map.
The reason it has been added to the map instead of augmenting transit is
that it would simplify the calculation of `message-id`, which in this
case is consistent for both old & new clients.
`chat-id` also represents the `chat-id` with respect of the sender, as
in 1-to-1 chats that is asymmetric.
Signed-off-by: Andrea Maria Piana <andrea.maria.piana@gmail.com>
Use the value of REACT_SERVER_PORT env var if set
Change node port and datadir depending on the value of DEV_BUILD config
variable
Fix missing paren
Bugfix
Remove desktopJSBundlePath
Signed-off-by: Vitaliy Vlasov <siphiuel@gmail.com>
reorganize config flags
remove offline-inbox-enabled? flag
remove universal-links-enabled flag
remove add-custom-mailservers-enabled? flag
remove spam-button-detection-enabled? flag
remove flags from config files
Signed-off-by: Eric Dvorsak <eric@dvorsak.fr>
Since offline inboxing and desktop were introduced, we went from testing with
~10 messages to ~1000 messages. This surfaced inefficiencies such as this issue.
It also means someone who joins a public channel such as #status will experience
significant lag when signing in. To remedy this, we put offline inboxing for
public/group chats under a flag until the underlying perf issue has been
resolved.
- Exposes behavior under QUEUE_MESSAGE_ENABLED flag that is turned off in
production.
- Delays messages to allow for reordering of latecoming messages up to 500ms
- Add `LOG_LEVEL_STATUS_GO` feature flag for a differentiated log level in status-go.
- Remove superfluous `DEBUG_LOGS_ENABLED` feature flag.
- Enable info-level logging for Jenkins and dev builds.
Signed-off-by: andytudhope <tuddy0525@gmail.com>
- Turns on flag for dev and Jenkins
- Change enode to peer in requestMessages arg
- Upgrades status-go to get ssh_requestMessages
- Use status-cluster enode
- Fix Android AddPeer binding bug
- DEBUG_LOGS_ENABLED flag enabled everywhere but production
- Adjust log level to conditionally show debug and RN logs
- PrefixHeader for sending app logs to Testfairy
- Asks for permissions on iOS at startup
- Introduce NOTIFICATIONS_WIP_ENABLED flag
- Surface FCM Token and put it in clipboard for QA manual end to end testing
- Listen for FCM RefreshToken event at root