Thank you for your response…@calldelegation
After bumping up forc to 0.48.1 the anomaly no longer happens, but there is a new kind of error. There’s actually an error thrown this time (progress).
The type is of the error is InvalidMetadataIdentifier…I did a search for this on the forum, Discord, and docs…but couldn’t find anything.
Have attached a screenshot
(also if you want to replicate locally here is the relevant commit).
I’ve linked to a specific commit because the most recent one in master is related to a separate issue