.app does not have an executable path after installing over an old build

Question

I have a TestFlight build that one user has downloaded, then we released a new version and they installed over that build. They got this error when trying to launch the app:

Answer 1

I encountered this particular error in a case where our normal app version were n.n.n and in the update we went to an app version that was n.n.n.n

We didn't have time to delve into it deeply but simply moving back to the original number scheme resolved the issue.