-
Notifications
You must be signed in to change notification settings - Fork 863
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
Fails to deploy contract with soroban-client to 0.2.1 and sorban 0.3.2 #72
Comments
I realized that in fact the project is using soroban 0.3.2, so I moved to that version and I had to fix initialize.sh Everything in the #74 PR |
So I am still very confused about this:
Following leigh recommendation the recommended setups say that: for this setup
So, after installing soroban-cli 0.3.3 I got the following error while ./initialize.sh When using standalone:
What I did is to use that docker version, in this commit and it did solve the deploy problem...
However, when running the front end:
|
First error, when Minting: After fixing it, I can say that Minting is working, however, apparently it does only mints 42 EXT?? When "approve and back up this project"
I guess that the error comes from trying to send the transaction to the wallet, because when minting it does gives a private jey |
My guess is that there is something wronw while building the transaction |
There are too many things here. This issue will onlye refer to "Failing to deploy contract with soroban-client 0.2.1"
So I'm opening a pull request for this: |
Pull request accepted |
What version are you using?
So, I was testing the new commit da61364 that uses soroban-sdk 0.3.2
I had different errors with different versions of
soroban-cli
With soroban 0.2.1, while running ./initialize, I managed to deploy the contract, but not to initialized it.
Then, I updated to soroban 0.3.3, and I did not even manged to deploy the contract. Got:
I was looking at the recent changes, and found that in the Docs it is used
Did the change to ./quickstart.sh and now works.
Will open PR
The text was updated successfully, but these errors were encountered: