The issues are not happening consistently. I'd be fine with removing but I prefer if we give the mobile team some time to figure it out and see if it can be improved.

prefer if we give the mobile team some time to figure it out and see if it can be improved.

Can we please remove for now, and then restore when it's improved? As it stands, it's blocking the development workflow for multiple people.

I sorted my more immediate problem by including npm run mobile-submodule-update in my build script.

Gutenberg includes gutenberg-mobile, which includes gutenberg, which includes gutenberg-mobile, which includes gutenberg

Seems like there has to be a better way

I know it's not great but my point is that we should try to be inclusive with the mobile team. Including their tests mean we don't break mobile inadvertently. We're all on the same boat, we should try to merge the repositories I think.

That doesn't mean we can't do quick wins for now.

I personally prefer this approach for now #11304

I personally prefer this approach for now

Yep, seems fine.