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.
React Native uses 'asl' to do logging, not NSLog, so we have to hook into that
to get logs sent to Testfairy. This means we get all the app device logs you
normally get in development, not just whatever happens in JS land.
- Modified default logging function when flag is set
- Delete Prefix header file and NSLog Macro
- 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
- 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