The latest revision was committed with version xxx of Mendix Studio Pro. Please install that version first.

0
Hi. When somebody in your team upgraded the project studio version then Studio will refuse to pull with the pop-up "The latest revision was committed with version xxx of Mendix Studio Pro. Please install that version first." (even if that version is already installed). I expected that Studio would fast-forward and re-open the project in the right Studio version, but it doesn't happen.   You have to: Launch that Studio version Open the project locally Agree to upgrade in place Make a local commit Pull Hope that the local commit will be skipped Shouldn't there be a smoother way?
asked
3 answers
0

If you don't have much updates in your local. I recommend deleting the project from your local and download the project using the upgraded Studio Pro version.

First, identify the studio pro version. 

 

This approach works when you don't have significant local changes and prefers a clean reset over resolving version upgrade issues manually. Also eliminates local conflicts. 

answered
0

Yes, there should me a smoother way, only using Studio Pro. But there isn't. You can put that in the idea forum :).

I usually use another Git client and upgrade the repository with that. But that only works if you don't have any changes to merge.

answered
0

Just open the correct new studio Pro version and open your local project. It will then convert your local project to that version and then you can do an update again. Or am I missing something here?

Regards,

Ronald

 

answered