Every second build is from an old version of the code

I think I've seen a comment on this before, but I've searched the forums and I can't find anything relevant.

Every other build, literally, shows an old version of the app with old data. It took a while to work out what was going on, and it's making it very slow to develop.

I've video'd what's happening, here: https://youtu.be/5wKbBN0gByM

Any help would be gratefully appreciated.

Thanks

Brian

dbrobert over 8 years ago

I think I've seen a comment on this before, but I've searched the forums and I can't find anything relevant.
Every other build, literally, shows an old version of the app with old data. It took a while to work out what was going on, and it's making it very slow to develop.

I'm not entirely sure I understand what you are trying to show in that video, but with SDK 2.1.4, Eclipse Plugin 2.1.5 and MacOS 10.12 (Sierra) I have noticed that some code changes require that I run the app twice to see the updates reflected in the simulator. And this has happened for me at least since the last release. I haven't dug in yet to determine if it's a Eclipse issue, an issue with the build process and/or compiler or if it's a simulator thing. But If that's what you mean then yes, I too have experienced that.

Cheers,
Douglas

BRIANBAN over 8 years ago

The video is just of me repeatedly pressing the run command. (Shift, Ctrl, Cmd F11 or something close to that).

It's showing that the build I'm expecting only works every other time. The alternate builds are from an old version of the code, with old properties, that must be cached somewhere, but I've searched disk with no luck.

It's very strange that it is _every_ second build.

dbrobert over 8 years ago

The video is just of me repeatedly pressing the run command. (Shift, Ctrl, Cmd F11 or something close to that).

It's showing that the build I'm expecting only works every other time. The alternate builds are from an old version of the code, work old properties, that must be cached somewhere, but I've searched disk with no luck.

It's very strange that it is _every_ second build.

Ah, okay. Then that is either the same thing I'm experiencing, something close to it or something related. I'm not sure how your simulator is flip-flopping between versions like that though.

I started playing around with making a small string change in my app and notice that the console will routinely report the following:

Could not open file: /Users/douglasr/develop/garmin/applications/testapp/bin/TestApp.prg Error: 1

And what is confusing is that the simulator restarts/reloads the app so it looks like the change is there but it isn't due to the above error. But if I run it again, it's fine. I wasn't able to get it to report that error twice in a row.

Cheers,
Douglas

travis.vitek over 8 years ago

I have seen situations similar to this in the past. I've always been able to eliminate them by closing the simulator, and deleting the %TEMP%\Garmin folder and starting everything up again. On a Mac, you should look for a $TEMP\Garmin folder and remove it.

Of course it might not hurt to delete the TestApp.prg file listed in the error message.

Hopefully that will help.

Travis

BRIANBAN over 8 years ago

I have seen situations similar to this in the past. I've always been able to eliminate them by closing the simulator, and deleting the %TEMP%\Garmin folder and starting everything up again. On a Mac, you should look for a $TEMP\Garmin folder and remove it.

Of course it might not hurt to delete the TestApp.prg file listed in the error message.

Hopefully that will help.

Travis

Thank you Travis.

cd $tempdir && rm -r GARMIN didn't help in my case (just tried that now), but it was a really good prompt to help me find where the files are being written to.

BRIANBAN over 8 years ago

I've rolled my code back to an older version that doesn't have one additional property/setting/setting config. That seems to have solved the problem, though probably with a combination of removing <temp>/GARMIN too. I'll see how I go adding it back in.