Failed to submit transactions after runtime upgrade

[xlc]

A few of our servers can no longer able to submit transaction after an upgrade of Karura. I think the cause is some old metadata was used to construct the transaction. Restart the server fixes the issue.

The same issue happens on polkadot apps as well. It no longer automatically refetch metadata after upgrade. It still displays the old spec version. We need to manually refresh the page.

Also got a few error reports from exchanges with similar issue.

[jacogr]

Are we 100% sure that subscribe_runtimeVersion works on parachains? In both cases that is what gets used and in neither case has the logic for that changed.

As I recall the specific subscription monitors :code under the hood and when that updates sends the updated version. Not convinced that is valid in this case.

EDIT: The simplest here is the apps UI, it subscribes, displays - https://github.com/polkadot-js/apps/blob/master/packages/apps/src/Menu/ChainInfo.tsx#L21 (So this is what makes me wonder around the subscription since you mention that the UI displays the older version despite being upgraded)

[xlc]

Let me do some test locally first.

[jacogr]

Closed by paritytech/substrate#9617

[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.