Resolve android pubky parity issues from #902#905
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Co-authored-by: piotr-iohk <42900201+piotr-iohk@users.noreply.github.com>
Co-authored-by: piotr-iohk <42900201+piotr-iohk@users.noreply.github.com>
Co-authored-by: piotr-iohk <42900201+piotr-iohk@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
|
@jvsena42 everything should be resolved now, please recheck |
|
There's few things around contacts addition (I guess could be addressed later, but did not mention it in any tickets)
Screen.Recording.2026-04-25.at.17.06.22.mov
Screen.Recording.2026-04-25.at.17.05.12.mov |
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
piotr-iohk
left a comment
There was a problem hiding this comment.
LGTM, to merge this.
Outstanding inconsistencies around contact addition/validation can be addressed separately, added to the ticket: #909 (comment)
jvsena42
left a comment
There was a problem hiding this comment.
Still see a divergence when trying to add an existent contact from home and from contacts
Screen_recording_20260428_070658.webm
@jvsena42 @ben-kaufman documented those in #909 (comment). I was thinking it could be handled in separate PR not to bloat this one - along with some other add/delete contact flow stuff (see: #909), but might as well be handled here. 👍 |
Agreed, this one has 31 modified files already. I'll keep testing |
resolves #902
Description
Preview
QA Notes
./gradlew compileDevDebugKotlin./gradlew testDevDebugUnitTest./gradlew detektto.bitkit.devon connected device2409BRN2CA