Solidity 0.5 Version: Alien Codex - Requesting new instance loop

[bergarces]

💻 Environment
Solidity 0.5 Version of Ethernaut (https://solidity-05.ethernaut.openzeppelin.com/)
Ubuntu 19.10
Chrome Version 78.0.3904.108 (Official Build) (64-bit)
MetaMask 7.6.1

📝 Details
When attempting to get a new instance for the Alien Codex level (19), it seems like a new transaction attempt to create a contract is issued after the previous one is mined successfully.

No other level seems to have this issue.

🔢 Steps to reproduce
Press the "Get new instance" button on the Alien Codex level (19) of Ethernaut with Solidity 0.5 and confirm the transaction with MetaMask.

[abcoathup]

Thanks, I have the same experience with Alien Codex level.

[CallMeGwei]

I'm also having this issue.

[CallMeGwei]

Workaround:

The contract is being created successfully. That fact, however, is not being registered in local storage.

One may manually edit the browser's local storage as a temporary workaround. (Accessing local storage data can be done in dev tools.)

Add the appropriate key:value pair to the ethernaut_player_data_*VERSION*_*PLAYER*.emittedLevels
object.

The level key is "0xf0D6F7dA4ed4Ff54761841e497F5aFc795F04688" and the value will be the instance contract address, which can be retrieved from etherscan via the tx hash.

[sacredwx]

same here

[xaler5]

Is still this an issue ?

[xaler5]

works for me

closing this since we already optimized local storage management . fell free to reopen if still an issue