Did you find a resolution to this one?
One of my Customers has been having this error message coming up incessantly since upgrading to 2.2.4 on the Desktop (they currently only copy up QVF's to the server at the last minute).
It is to the point of being a major problem for them.
If anyone has any pointers I would be pleased to hear them.
Unfortunately, no. The problem is 80% present, and its effect is only 80% predictable.
20% of the time, the app will open and reload without any complaint.
When the error message occurs, the app is usually saved with the new data. Sometimes it isn't. So I have to go and check the app against the newest source data to make sure that it is now present.