App designer break points doesnt work

I designed GUI via appdesigner. I copied that app to another computer. Both computer has same matlab 2023a version. Everything is same. But in another computer I can not set break points in appdesigner . Why that happen? Code is same, not different, same file.

[dpb]

Impossible to diagnose from afar with just a generic description; would have to have the .mlapp file to tell.

However, one might guess that a compilation error has inadvertently been introduced into the second copy; that's the most common reason breakpoints can't be set in the editor.

[Melih Furkan SEN]

but I use exactly same folder and file in both computer. Same version of matlab 2023a as well. One of the computer allows me to do breakpoints. Another one doesnt

[dpb]

Is it THE same file from a shared location or a copy? If a copy, there's always that chance that you've inadvertently made a change in the code.

As noted before, something of this sort is impossible to diagnose from afar without the actual .mlapp file (and may be even with it, but if the symptom doesn't appear on another system, it would imply it's the system that has the problem, not the app).

Can you create a new app file and set breakpoints in it on the second machine? If so, that returns the issue to one of something in the specific .mlapp file; if not, then there's something wrong in the install itself.

[Melih Furkan SEN]

I can set breakpoints in new files. However due to "unknown changes" made in the existing file, the app acts like "only creator can set breakpoint"

I have removed and copied again and again exact same file with no change has been done. There cant be compile error because app works in other machines as well. But you cant set up breakpoints. I dont think that I would be able to run the app if there was an breakpoint error

[dpb]

"..., the app acts like "only creator can set breakpoint""

What does that mean? Are you getting an error message of some sort that has such a phrase in it? Post graphic of it, if so.

That sounds like an issue of an OS protections being set that some file location can't be accessed or somesuch. A <recent Q? here on a file access error> turned out to be caused by a symlink pointing to the file; any chance there are such in the install directories or at the location of the .mlapp file on the wayward system?

You probably will have to submit this to official TMW support to resolve; it simply can't be diagnosed remotely without more details than we have.

[Melih Furkan SEN]

I dont get an error.

I just simply can't set break points because its greyed out.

In computer that I created the app, I can set break points.

I copy same file to different computer which has same Matlab 2023 version , I can not set breakpoint in app. Its greyed out

Answer 1

[Melih Furkan SEN]

I have found solution.

you press "ctrl + s" multiple times and break point gets fixed

Answer 2

[Dan Harris]

Not sure this is your issue, but I had a very similar issue. I copied via github clone from one machine to another with different matlab versions 2023a to 2021b. I got the same error about unsynced versions because MATLAB had to make changes to make the .mlapp work on 2021b. To solve this issue I had to saveas "new file name", then saveas "old file name". A simple save or ctrl+s wasn't cutting it. Once I overwritten the old file, I was able to break in the .mlapp code again on the new machine.

[Melih Furkan SEN]

So you did "save as " twice? I tried and didnt solve. Also both computer have same version of matlab

[Ben Abbott]

@Dan Harris, your suggestion worked for me. However, for me, the problem did not coincide with a version upgrade/downgrade.