-
Notifications
You must be signed in to change notification settings - Fork 79
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
Validation failed for transaction because of invalid properties [group] #17
Comments
Added a bit more log and the error in that task is an HTTP 502. It seems unrelated to the issue in the front end. |
@paulosuzart did you solve this problem? |
Not solved yet. Thank you. |
this related group id in algosdk. so frontend problem. |
Hi, everyone, just wanted to say I am also running into this issue, any help would be appreciated 🙏 |
Btw, are you using Algosigner or MyAlgo as wallet?, it happens with both wallets? I am using algosigner because I couldn't connect with MyAlgo wallet (because of another error). |
please debug in frontend, you will see issue. you have to convert Transaction address with Uint8 array. |
Hey all, after running locally following the README, I managed to connect with my wallet, but then when I click deploy contract I get:
The head commit of master branch I'm using is
e1b7e469aa1df99958d55e821dd673b281cdd620
.Steps to reproduce the issue:
After the celery worker throws:
And the frontend enters to the
#/admin/add-nft/f7b91685a185449e9ad77d699b78ea48?start=true
where you can see the asset but then upon clicking Deploy Contract the message in the title of this issue is displayed in the console.I tried to tweak the front end to see what is happening but couldn't do much. I found a more or less related topic https://forum.algorand.org/t/validation-failed-for-transaction-because-of-invalid-properties-group/5330.
I can't find the source of the error in the backend. Also not sure if the error in the front end is collateral, or if they are completely unrelated.
Environment: Ubuntu 20, Python 3.9.9, SQLite, PureStake credential correctly set. Some of the related transactions found in the explore. Happy to provide more details and try to help more. Thanks
The text was updated successfully, but these errors were encountered: