Apps: Upload button does not work for contract ABI

[lana-shanghai]

Hello! I'm connected to Canvas testnet. The contract ABI is recognized, but the upload button is grey. Please see attached image

[jacogr]

Did you add a .contract file or a .json (ABI-only) file?

Seems like flipper above?

There is a bug I found yesterday actually, when initially you add a .wasm file to the JSON (or anything invalid), and then add the JSON/ABI, it does't quite allow you to add the was next. In that case, this does work - remove the ABI and re-add.

(Should have a fix for this specific case later today once the cause was figured out, but the work-around would be to remove, re-add.)

[lana-shanghai]

Well previously there were two separate lines for the .wasm and the .json files, and now it only asks for the ABI. Yes, it's Flipper, I'd like to know how to deploy before I try to deploy anything more complicated :D

[lana-shanghai]

OK, now I see the WASM line. Thanks for the help!

[jacogr]

Ok, so just clear, re-add, think you ended up with that weird wasm-first upload doesn't-reset issue.

The reason for only the single field currently is that the .contract file actually contains both the ABI and the WASM - so it is a single upload when available. (I believe ink! creates it automatically now)

[jacogr]

Will leave it open and close with the fix for whatever cause the weirdness.

[lana-shanghai]

How do you generate a .contract file? I ran the cargo contract generate-metadata and it produces only the .wasm and the ABI... No? I upgraded ink! to the latest.

[jacogr]

It is very new, see the request for support - https://github.com/polkadot-js/apps/issues/4010

[cepwin]

I am having a similar error now with the new 2-page upload for contracts. I went so far to clone the code to my system and run it locally and I still have the error....I go to the first page upload flipper either with .wasm and the .json or .contract...either way when I go to the second page I can not let the deploy button to become active. Last week with the 1 page deployment it worked just fine. The impression I get from this bug report is it was closed so could I be doing something wrong....if I am I don't see it.

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.