Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TESTING] IOS private key function #594

Open
10 of 18 tasks
Peppermint1020 opened this issue Nov 27, 2024 · 1 comment · May be fixed by #591
Open
10 of 18 tasks

[TESTING] IOS private key function #594

Peppermint1020 opened this issue Nov 27, 2024 · 1 comment · May be fixed by #591
Assignees

Comments

@Peppermint1020
Copy link
Collaborator

Peppermint1020 commented Nov 27, 2024

Testing scenario:
Success scenario:

  • restore by google drive

  • restore by seed phrase

  • restore by key store

  • restore by private key

  • restore by seed phrase with custom path and passphase

  • restore seed phrase from prod version
    error scenario:

  • restore by google drive with wrong address: error message

  • restore by seed phrase with wrong address: error message

  • restore by seed phrase with wrong derivation path:error message

  • restore by seed phrase with derivation path,but didn't input derivation path:error message

  • restore by seed phrase with wrong passphrase: ?

  • restore by private key with wrong address: error message

  • restore by google drive with wrong password: error message Decrypt failed

  • restore by invalid seed phrase:error message
    no error message

  • restore by wrong keystore json file:error message

  • restore by key store with wrong password:error message

  • restore with invalid private key: error message

  • No backup in google drive alert

Note:
(1)We need hide iCloud method as we only provide this method in lilico wallet.
Image
Image
(2)The text content is incorrect, should maintain consistency with the design.
(3) The number of account is different the the actual counts.
Image
(4) No error message when use invalid seed phrase.
(5) App stuck when restore seed phrase from prod version without input address.
https://github.com/user-attachments/assets/df2ebd87-ad3a-4d65-af8d-80aeaaa61b9b
(6) When user input wrong address, we need pop up error message: "cannot find this key under this address"
https://github.com/user-attachments/assets/b6b43bfa-a93f-4d92-bf5a-ac1363617bf6
(7) If is seed phrase with derivation path, but not input derivation path, need pop up error message:
(8) For key store with wrong password, need pop up error message
(9) For key store with invalid json file, need pop up error message
(10) When input private key, the page stuck in loading state

ScreenRecording_11-27-2024.16-18-56_1.MP4
@Peppermint1020 Peppermint1020 self-assigned this Nov 27, 2024
@Peppermint1020 Peppermint1020 converted this from a draft issue Nov 27, 2024
zhouxl added a commit that referenced this issue Nov 27, 2024
@Peppermint1020
Copy link
Collaborator Author

Peppermint1020 commented Nov 28, 2024

Tested on ios dev version 2.3.0(4).
Update: Tested on iOS dev version 2.3.0(5)

  • We need hide iCloud method as we only provide this method in lilico wallet.

  • The text content is incorrect, should maintain consistency with the design: Remove " icloud" from text content![Image]Image
    Update: Correct on iOS dev 2.3.0(5).

  • The number of account is different the the actual counts.

  • No error message when use invalid seed phrase.
    Update: Correct on iOS dev 2.3.0(5).

  • App stuck when restore seed phrase from prod version without input address.

  • When user input wrong address, we need pop up error message: "cannot find this key under this address"

  • If is seed phrase with derivation path, but not input derivation path, need pop up error message:

  • For key store with wrong password, need pop up error message

  • For key store with invalid json file, need pop up error message

  • When input private key, the page stuck in loading state: This issue solved, will pop up error message when user input invalid private key
    Improvement:
    (1) Now we have two different error message popup, should we only use one of these?
    When input customised seed phrase without derivation path:
    Image
    When input seed phrase with wrong address:
    Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In QA
Development

Successfully merging a pull request may close this issue.

1 participant