- separate zh_hant to zh_hant_tw, zh_hant_hk and zh_hant_sg
- add new locales `zh-hant-sg`, `zh-hant-hk`, `zh-hant-tw`
- fix zh_hant and zh_hans typo and layout
- update `bots/browse/translations.js` `bots/console/translations.js`
`bots/mailman/translations.js` `bots/transactor/translations.js`
- 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
- protocol/web3/inbox: make request-messages work by adding enode peer,
generating and using symkey, and finally using raw CallRPC for
shh_requestMessages.
- protocol/core: Clean up log lines
rename test
fix test `supported-locales-are-actually-supported` and improve failing message
fix some coding standards
rename old `str` namespace alias to `string`
fixing cs
rename translation id to label and explain checkpoints
remove non-existent labels in translations
add some comments
add status 0.9.12 as first checkpoint in translations, plus current supported locales
remove non-existent label from base checkpoint and fix locale->checkpoint and supported locales
format checkpoint-0-9-12-labels in several lines
add fn labels-that-are-not-in-current-checkpoint
previous behavior was using context (which screen we were on) to
determine if account was new or not.
in order to be able to have more straightforward automation this
commit now checks the list of accounts to get that information
which is more accurate and allows to login without navigating screens.
This fixes bugs #2520 and #2484
The cause of the bugs is the fact that calling `.sorted` method
on the realm resultset produces another resultset which is sorted
when iterated through `Iterator<T>` interface, but does absolutely
nothing to way how resultset object is serialised (printed out
as JSON).
So when we sorted, printed to json, parsed back through transit
and expected the order to be retained, it was not, and it was
failing quite randomly.
To be precise, it failed in a case where we sorted the resultset
according to some property and picked the top element from the result.
As the top element picking was done AFTER the sorted realm resultset
was converted into cljs datastructure, it was sometimes failing.
This fix just ensures that we select the single element from js
resultset (where sorting info is still retained) and only convert
that single element to cljs (it's also much more efficient).
We want minimial scope for 0.9.12b release so only relevant migrations made it
into that. To ensure a happy upgrade path in future versions, other v17
migrations (all related to pending messages) have been moved into v18.
This means develop will break for current developers, but 0.9.12 -> 0.9.12b
-> (next version / develop after this commit) will work as expected.
Grammar fixes, consistency across contexts, and some good ol' content changes.
Some minor content changes for better, clearer explanations.
Lots of spelling and grammar changes.
Most of the grammar changes were to capitalised letters (which I have made at least consistent in different contexts) and whether or not the prompt ends with a full stop (again, context dependent)
status: ready
- in unsigned transaction tab, show the transaction sent screen when user
signs a transaction
- in send command flow, show dialog when users want to sign later
This PR fixes the fact, that `[:wallet :send-transaction]` path
in db was not properly cleared in some cases, which demonstrated
as couple of the subtle issues (like that you were taken straight
to the signing state on tx-modal in when sending `/send` command
and some tx was sent previously from wallet, and some quite serious,
like #2197, which was caused by password info not properly cleared
between multiple invocations of the `/send` command.
- makes it possible to hide the tabs in a view under certain conditions (e.g
when the keyboard is displayed)
- hide tabs in main screens when the keyboard is displayed
- fix bug where toolbar wasn't ready with zero statuses
- fix toolbar center and margin to top
- fix grey background missing
- fix top status text margin from the top of the card
- fix separation lines between statuses edge to edge
- margin with chat icon to bottom 12
Also apply same to popular hashtags for consistency
Addresses all non-test must haves except "All content hidden behind right edge on smaller screen (check 5s)"
- Main screen (empty): fix topbar margin
- Main screen: Font size name (and dapp list item)
- Main screen: Get rid of popular hashtag border
- Main screen: All for DApps should be blue
- Main screen: tap on number of popular hashtag -> error
* Upgrade status-go to bugfix-no-messaging-rinkeby-gd04e667-12 (geth 1.7 rebase)
* [bug] fix#2089 and #2098 with geth update
with geth 1.7 addresses are passed with 0x prefix and mix of lower/upper cases
update the normalize hex function so that addresses are always without prefix
and entirely lower-cased.
previously one would get a red screen in develop and probably a white screen
in the app
now it shows a label indicating that the transaction has expired
- Refactor: more consistent styles naming
- Align text next to icon
- Grey background whole discover
- Set background popular apps
- Fix margin-bottom for all-dapps
All styles belonging to screen/component should be in styles.cljs. This commit
moves platform specific styles to appropriate place.
Also fixes misc weird ns imports.
Also moves colors to common ns (FUBAR).
- Move permission check from main screen (no longer makes sense given
choose recipient is reached from send)
- Add ios-specific display and permission checks
The flat-list component handles the nil case but the precondition does
not.
This is currently causing transaction list failures when the list of
unsigned transactions is empty.
- Use flat-list and 3 column layout for grid
- Get rid of platform ns dependency
- Minor refactor: "wrap" -> :wrap, backgroundColor -> background-color
Disable screen while transaction is signing
Add handling for incorrect password on signing
Fix bug where spinner doesn't appear on the second time
Address feedback
More rebase fixes
Fix spec failure
this fixed involved changing the swiper so that a function can be passed as
title instead of a string.
this allows developpers to pass custom elements as titles and still use style
and variables that are computed when tab is built
* [design] remove syncing animation outside of chat views
replace no-sync-bar? parameter by show-sync-bar? parameter as not showing
the sync bar is the norm and showing it the exception (only appears in chats)
* add suscription and spec for sync-state
[bugfix] transaction details background should be white
[bugfix] button styling in unsigned transactions
[bugfix] make whole item touchable in transactions history and unsigned
[bugfix] correction of icons styling in transactions history
[bugfix] error message should not touch the toolbar in wallet
[bugfix] add asset icon and text are different on ios and android
PR review fixes
- Update toolbar text
- Add frame for camera/qr
- Add button for choose contacts
- Add button for address from clipboard
- Add button for browse photos
Set recipient from clipboard.
Added functionality and event handling necessary to set recipient
from clipboard.
Add choose-recipient event to assoc into the database
Add QR code scanning to first screen
Add vector icons for copy and select image
Fix svg
Fix rebase, localize labels
Add checkmark icon (this is a placeholder, current svg won't render)
Remove leak from develop
Vertical alignment fixes
Vertically align maps in view
Address review comments
Fix rebase reference problems/styling issues
Small style tweaks, fix icon
Fix small design issues
Indentation fixes
Address review points
Fix indentation
Prevent permissions request on ios
On ios, a permissions request results in a null reference error,
do a platform check before performing a permissions request.
Fix compile error
Restyle for ios, colours, layout
Update icons on ios
Restyle disabled button
Browse photos button disabled
Add viewfinder and platform specific styling.
Viewfinder and style changes
Add some torch functionality, fix toolbar, style issues
Refactor view style, add translucent bits to viewfinder
Address pull request feedback
Replace a style by defstyle
- Update toolbar text
- Add frame for camera/qr
- Add button for choose contacts
- Add button for address from clipboard
- Add button for browse photos
Set recipient from clipboard.
Added functionality and event handling necessary to set recipient
from clipboard.
Add choose-recipient event to assoc into the database
Add QR code scanning to first screen
Add vector icons for copy and select image
Fix svg
Fix rebase, localize labels
Add checkmark icon (this is a placeholder, current svg won't render)
Remove leak from develop
Vertical alignment fixes
Vertically align maps in view
Address review comments
Fix rebase reference problems/styling issues
Small style tweaks, fix icon
Fix small design issues
Indentation fixes
Address review points
Fix indentation
Prevent permissions request on ios
On ios, a permissions request results in a null reference error,
do a platform check before performing a permissions request.
Fix compile error
update react-native-swipper to latest working version
remove bottom margin hack in other screens with similar bug
fixes Cannot scroll transaction history when app is syncing #1902 as well
* Fix#1886
Completly rework the way how async handlers work
Delay further processing of message till async handler returns result
* Fix indent
* Fix#1903
In release 0.9.11 we'll have v13, so we don't want to modify this in develop.
This moves Push notification related changes into a new migration as opposed to
merging them into one.
- Send notification when sending message in 1on1 chat
- Add notify FFI with binds for ObjC and Java
- Add fcm-token to contacts in spec and realm
- Add notifications to db
- Include fcm-token in contact request
- Update fcm-token when it arrives and put it in DB
- Disable copy-paste hijacking and popup
- Turn on notifications flag in Jenkins build
* Implement possibility for async command handlers
Command handler can now return results asynchronously,
and those results as saved and persisted, indexed by
command message-id.
* Address feedback raised in PR comments
* Different handler codes + simplified error message
cljs-priority-map provides a special purpose data structure that needlessly
complicated things and doesn't appear to provide much value for what it gives
us.
Instead, keep :chats an ordinary map and sort vector on final subscription, as
our ListView destructures data-source items correctly.
This means we can upgrade Clojurescript.
- After testing we don't need to expose this WIP with popups etc
- get-fcm-token event was accidentally included twice during rebase leading to warnings
- 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
fix wallet errors that were sticking when refresh occured
add separate errors for transaction history fetching with visual feedback
update wallet when going on wallet tab
update transaction list when opening transaction modal
- Add wallet key to db
- Add sub for wallet error messages
- Add event handlers to set wallet values
- Cover the above with tests
Oh and add the tests
Add error view
Add exclamation mark, style error message, add message to view
Remove commented styling
Localise wallet error
Add translation
- Add an english translation for the error message
- Change error representation in db to a keyword
- Update handlers to set and clear keywords
Constrain spec, make view conditional
- The spec for error messages now takes a predefined set.
- Error message only pops on error
Fix test
Align maps
Reduce event chain size, move logging to timbre
- Print FCMToken which can be used to send PNs from Firebase Console
- Include react-native-fcm and related packages
- Update capabilities for iOS
- google service config files for Android and iOS
The ```:account-update``` event was being passed the key
```update-status?``` which has nothing to do with an account as
represented in the db. This resulted in a spec failure when this
key was detected on an attempt to save changes.
I've sanitized this event by pulling out the three account keys,
```[:name :photo-path :status]```
that are relevant to ```profile``` and ensuring that only they get
passed to ```:account-update```.
Profile updates now work as expected.
Add tests covering profile events
Fix the runner
Currently account recovery includes whitespace on either side of the
passphrase, preventing recovery of the desired account.
We trim that whitespace in the account-recovery-fx
Initial utility for live data binding in the new wallet.
- Add prices namespace to get fiat prices from Cryptocompare
- Events to init wallet balance and load prices
- Listen to these events in wallet main view
- Show accurate ETH balance, USD value and %change from yesterday
- Enable wallet tab in Jenkins
Mapview component accepts the `:initialCenterCoordinate` which always must have
longitude and latitude attributes. This ensures that they will always be present
even when they are missing from the map passed retreived from the app state.
Also accomplished was removal of redundant preview loading
and command markup is now stored as cljs data in app-db,
only being translated to RN components in subscriptions
This commit ensures messages are ordered correctly when participants join and
leave a group chat. Specifically, the last received message will appear last.
Previously the user and chat clock was queried and updated in an ad hoc manner.
With this change there are only two clock changes to keep track of:
Sending messages:
time = time+1;
time_stamp = time;
send(message, time_stamp);
Receiving messages:
(message, time_stamp) = receive();
time = max(time_stamp, time)+1;
(See https://en.wikipedia.org/wiki/Lamport_timestamps)
Note that this means we can get rid of all the non-message clock queries and
updates.
Transactions with 15 significant digits crashes the app due to something weird
going on in the Clojurescript -> web3 -> BigNumber chain. This fix converts the
number into a BigNumber before converting it into Ether.
When the input field includes an unmatched " in the input-text, there's a
mismatch between the parsed command-args and the length of the text field,
causing text selection to be out of bounds. By bounding the new selection to a
maximum of the input text, this is avoided.
A single unbalanced ')' shouldn't count as nesting, so ')' and 'a)' etc don't make the form ''.
console: add ad-hoc test script for suggestions
This creates a quicker feedback loop for testing console suggestions, as well as making sure we don't introduce suggestions regressions.
chat, parameter-box: hide parameter-box when {markup: null} is returned
to and from props in context in suggestions function
ability to send request using text-message property in handler and via status.sendMessage
show request's text if it exists
Made a semantical correction for "left" which at first was interpreted as having to do with direction, where actually it was about "leaving".
Made a grammatical correction relating to singular plural usage.
Made comment consistent.
Tried to do it on mobile 2 hours ago and ended up accidentally deleting it...so again:
changed "formal" you to "personal" you as thought it would fit better.
changed several changes, small as well as big ones
will need to play around with the app more to be sure if i interpreted the constellation of some of those translations correctly
"Hey guys I/we kinda thought whats the best way to advertise your project if not being able to tell that your supporters are actually so dedicated they will even translate your app into a dead language? (I mean there are propably a million better ways...but still)
WE/I DID IT!
With the best of our/mine school latin and some dictionaries we translated Status into LATIN ! "
* chat: fix broken chat delete logic
Previously, persisting the chat delete functionality was working
only for group chats, where the `debug?` flag decided if delete was
a real "hard" delete (deleting data from the realm database) or just
marking with the `inactive` flag.
However non-group chats were not deleted at all, which I believe is a
bug fixed by this commit.
* chat: fix broken chat delete logic
Fix the branching logic with `if` instead of `when`
* Make sure suggestions properly popsup when command starts with space
* Added basic tests for splt-command-args
* Properly handle white spaces
* Added tests for commands with whitespaces