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

Unable to perform swap on 1inch.exchange if initial swap was cancelled by closing bottom sheet #12920

Closed
churik opened this issue Dec 15, 2021 · 2 comments · Fixed by #12978
Closed
Assignees

Comments

@churik
Copy link
Member

churik commented Dec 15, 2021

Bug Report

Problem

After cancelling swap on 1inch.exchange unable to complete it again ("Unknown error" on tapping on Swap)
Is not reproducible on MM / Chrome.

Expected behavior

can see the bottom sheet again

Untitled.mp4

Actual behavior

Unknown error;
On Android can again start the process after re-login, on IOS couldn't find the way to proceed

Reproduction

  1. Restore multiaccount with funds
  2. Open 1inch.exchange, connect wallet
  3. Tap on "Swap"
  4. Tap on Cancel
  5. Tap on "Swap" again

Additional Information

  • Status version: 1.18
  • Operating System: Android, iOS
@flexsurfer flexsurfer self-assigned this Jan 3, 2022
@flexsurfer
Copy link
Member

seems like that happens because personal_ecRecover returns undefined

@flexsurfer
Copy link
Member

CALL RPC personal_ecRecover nil : #js {:jsonrpc 2.0, :id 10, :error #js {:code -32700, :message method is unsupported by RPC interface}}

flexsurfer added a commit that referenced this issue Jan 6, 2022
flexsurfer added a commit that referenced this issue Jan 11, 2022
… cancelled by closing bottom sheet

Signed-off-by: andrey <motor4ik@gmail.com>
qfrank pushed a commit to qfrank/status-react that referenced this issue Jan 28, 2022
… swap was cancelled by closing bottom sheet

Signed-off-by: andrey <motor4ik@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants