Deployment bug while L1->L2 erc20 bridging

[adaki2004]

Describe the bug

Jeff reported that the invokeMessageCall() always fails during L1 to L2 ERC20 bridging.(The other way it works !!).

I recalled that we faced this issue during testing so we mocked the Bridge and InvokeMessageCall() in a way of directly calling the encoded function (in message.data).

@dantaik Do you remember this convo ?

It seems it might not be a forge-foundry issue but how chain handles the deployments with the new keyword.

As in A3, the deploymet was with Create2Upgradeable I'd go back to this:

Steps to reproduce

Steps to reproduce here.

Additional context

Additional context here.

[cyberhorsey]

I am unsure if this is the issue or not, but I will try a deployment of the previous deploy erc20 code and see if it works.

[cyberhorsey]

Oh and note this same issue reappears on retryMessage, and whether it's claimed by relayer or by the bridge UI.

[davidtaikocha]

Closed by #14621