- 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
- Correctly parameterized PRODUCT_BUNDLE_IDENTIFIER
- Automatically set architecture based on hardware available
- Update iOS deployment target to 8.0 (minimal deployment target for latest Xcode)
- Enable recommended warnings (infinite recursion, etc)
- Enable Testability for debug configuration
Podfile updated to version 8.0 target, as this is assumed by default with this warning:
"[!] Automatically assigning platform ios with version 8.0 on target StatusIm because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`."
- 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
Oskar Thorén
Julien Eluard
Eric Dvorsak
Andrey Shovkoplyas
Anton Danchenko
antdanchenko
Goran Jovic
vojta
angusiguess
Chris Hutchinson
Gustavo Nunes
ankit raj