-
Notifications
You must be signed in to change notification settings - Fork 13
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
Why Developer
tab got removed from parachain's Settings?
#269
Comments
would like to know where the custom types have to be added for the respective chain |
paritytech/substrate#8615All chains including this change in substrate no longer need to manually set custom types 🎉 If you need this dev tab for older versions, run a local older version of the apps UI that includes it. It is never a blocker if you run the version matching the cumulus tutorial guide's one. You can see the history of tested ones here in the 1st page history: |
@nukemandan I upgraded codebase to 0.9.11 and also implemented https://github.com/substrate-developer-hub/substrate-parachain-template/blame/70b63ad47a0255c667c6b3329fce92bebb369b3a/pallets/template/Cargo.toml#L16 in all pallets to fix compilation issue. Parachain is also able to connect with local relaychain and producing blocks. Are you suggesting to test my upgraded parachain(0.9.11) with older version of PolkadotJs.apps? |
No I am saying you no longer need custom types. Try it ;) |
@nukemandan Its not working. I have opened new issue #271. Please see and let me know if I am missing anything |
I was doing local testing by connecting with local relay chain. I was able to connect with relaychain as parachain. Parachain was also producing blocks.
However I am not able to execute extrinsic because of Polkadot JS issue.
I just checked this tab got removed from all live and testnet parachains's settings.
It's visible only under solochain. Because of this issue, I am not able to import custom types and hence not able to perform any extrinsic.
This is a blocker and I can not proceed due to this issue.
The text was updated successfully, but these errors were encountered: