- Changelog updated
[#1126] Release 0.3.0
- Version updated to 0.3.0 build 1
[#1126] Release 0.3.0
- The release needed to be increased to 1.0 build 3 because we already uploaded 1.0 build 2 in the past
Update CHANGELOG.md
Co-Authored-By: Honza Rychnovský <rychnovsky.honza@gmail.com>
- New target for Testflight & AppStore builds has been created
- Automatic dSYM upload run script added to the configuration of the target
- DebugMenu is no longer accessible in production builds, only Testflight builds
- The issue has been solved with setting the fixedSize() modifier. That one ensures the word is never truncated. I tested the seed words on iPhone SE and it fits the screen even when I repeat the words three times, e.g. "humanhumanhuman". It works well.
- Pull to refresh feature has never been required or designed by Product or Leadership, it was a temporary thing that helped during the development but has been completely replaced with reactive approach over the time.
- copy with expiry time set draft
[#1097] Zashi-iOS audit Issue E
- copy to pasteboard has been removed from recovery phrase seed completely
- copy seed to pasteboard added to the debug menu, please note, the debug menu will not be in production build, issue #1113
- draft
[#1086] Resolve interaction with the keychain for both fore and background app states
- revert
[#1086] Resolve interaction with the keychain for both fore and background app states
- initialization pipeline updated to handle state when BGTask runs with fresh app start, in such case Zashi wait and doesn't try to initialize SDK -> no keychain error is triggered
[#1086] Resolve interaction with the keychain for both fore and background app states
- code cleaned up
- finished the state handling
- closing the BGTask asap for state that is supposed to just wait
[#1086] Resolve interaction with the keychain for both fore and background app states
- unit tests fixed
[#1086] Resolve interaction with the keychain for both fore and background app states (#1091)
- Comments addressed
[#1086] Resolve interaction with the keychain for both fore and background app states (#1091)
- Unit tests fixed
- Block time of didFinishLaunching increased to 0.5s (from 0.02)
- The available balance 0 scenario is now handled on a product/design level and the 0 is replaced with a progress view.
- There is some redundancy in the code that is going to be resolved in #1087 because it will require to implement a brand new reducer and stream subscriber, out of the scope of this issue.
[#1055] Handle unavailable AccountBalance
- Changelog updated.
[#1055] Handle unavailable AccountBalance (#1088)
- rebased
- All bullet points from the parent ticket have been resolved
- The keyboard is not decimal one so users don't need to switch to numbers + it reduces cases when users fill in some alphabetical letters + it improved the UX with floating point comma vs. point
- Error handling fixed
- Max amount fix and rely on spendable balance
- Unit tests fixed
- MessageEditor updated to present disabled state in a different way
- Text in the memo is not persisted when the transparent address is used and MessageBox disabled
- New unit tests implemented and many more updated
[#1060] Memo field behaviours for transparent address (#1075)
- comments addressed
[#1060] Memo field behaviours for transparent address (#1075)
- debug code removed
[#1060] Memo field behaviours for transparent address (#1075)
- code revert
- new layout for the scan screen
[#988] Scan UI
- new layout and design for scan
- camera not authorized case + UI
- scan store refactored to the latest TCA
- unit test fixed
[#988] Scan UI (#1069)
- changelog update
- ZashiBackModifier updated with a new hidden param. This way it can be controlled by views for dynamic scenarios.
- Reducer updated to latest TCA.
- Unit tests refactored and fixed.
[#1037] Consolidate back button on the phrase display screen
- updated test
Lukas Korba
Lukas Korba