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

Offramping twice in a row fails #370

Open
Sharqiewicz opened this issue Jan 13, 2025 · 5 comments
Open

Offramping twice in a row fails #370

Sharqiewicz opened this issue Jan 13, 2025 · 5 comments
Assignees
Labels
type:bug Something isn't working

Comments

@Sharqiewicz
Copy link
Contributor

Sharqiewicz commented Jan 13, 2025

Context

I wanted to offramp USDC from Base.
I connected Coinbase Wallet.
After I returned from Mykobo this error appeared:

Error in squidRouter: ContractFunctionExecutionError: The contract function "approve" returned no data ("0x")

This could be due to any of the following:
- The contract does not have the function "approve"
- The parameters passed to the contract function may be invalid, or
- The address is not a contract

How to reproduce

@Sharqiewicz Sharqiewicz added the type:bug Something isn't working label Jan 13, 2025
@pendulum-chain pendulum-chain deleted a comment Jan 13, 2025
@prayagd
Copy link
Collaborator

prayagd commented Jan 16, 2025

@Sharqiewicz is this fixed?

@Sharqiewicz
Copy link
Contributor Author

@prayagd Let me check

@Sharqiewicz Sharqiewicz self-assigned this Jan 17, 2025
@Sharqiewicz
Copy link
Contributor Author

@prayagd It is happening when you try to offramp 2 times in a row. This is related to incorrect clearance of the state

@ebma ebma changed the title Offramp on Base failed Offramping twice in a row fails Jan 22, 2025
@ebma
Copy link
Member

ebma commented Jan 22, 2025

@Sharqiewicz thanks for flagging this 👍 Can you please fill in the 'How to reproduce' section in the description of this ticket so it's clear to everyone what the bug is?

@ebma
Copy link
Member

ebma commented Jan 24, 2025

@pendulum-chain/devs we concluded that this was due to an RPC issue, correct? Shall we close this ticket as it was kind of fixed with #404?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants