Hey @maxosh, thank you so much for these files and videos–they are so helpful! I assume that since you’re working on two different machines, you probably downloaded the latest published version of your files from Axure Cloud to avoid the hassle of moving them between machines; is that right?
The first video, “Screenmovie of publishing” shows a publish dialog of the file that is not connected in any way to Axure Cloud; that’s why Axure creates a new instance of your file when publishing it:
In a second video, “Screenmovie on imac everything works fine”, I see that although the file looks identical, you probably opened a locally saved file, and this file is connected to Axure Cloud via the share link:
To sum up: when you download a .rp file from Axure Cloud, there is currently no connection link to its place in the cloud, so Axure Cloud treats it as a brand new file when you publish it. In this case, replacing a copy of the existing file might be a solution. I understand that it might not be ideal, so I will pass this feedback on to our product team to research whether we can fix it. If you open a locally saved file, then the link is in place so that you can publish it without the issues.
Using the Teams functionality might be a solution too. In this case, once you create a team project, the central copy of your project will be stored on the server, and you will need two local copies of this project stored locally on both your machines. These copies will be linked to your central copy so that whenever you check in, all changes are sent to your central copy.
I hope this helps!