Ticket Created
over 3 years ago

WERETECH-11158 (SDK Manager not working in Ireland)
WERETECH-11159 (Spaces in path break simulator)

SDK Manager error

Hi,

Since the SDK 4 was released, I was having issues making my watch faces work on the Venu 2 using the new SDK. I got past the createBuffer part with the help of the SDK announcement thread, but after that was solved, I was still getting errors like setColor not being recognized, which was very weird. So I decided to start using VSCode to see if it would make any difference to those weird errors.

So first I tried leaving Eclipse installed and go about the process of getting VSCode set up. I made a copy of my Eclipse project to another folder and was able to open this as a VSCode project. I installed the plugins, configured the MonkeyC settings and ran the simulator, apparently with no issues whatsoever. However, I started to make changes to my code and they were not showing up on the simulator, like the simulator was still running Eclipse's version of my code. Then I decided to create a new watch face project from scratch in VSCode and when I ran it, it was still running my old project from Eclipse somehow? It's like the data from VSCode was not being sent to the simulator and it was still running whatever it had in cache/memory from Eclipse.

Then, my next try was deleting Eclipse (including * ~/eclipse, * ~/.eclipse and * ~/.p2) and the SDK manager (including Garmin folder in AppData/Roaming where the SDK and devices are downloaded to) completely, to start everything from scratch. Sadly none of those have uninstalls in "add or remove programs", so I deleted them manually, all the folders that I could find. I downloaded the SDK files from Garmin again (just in case they've been updated) and extracted the files from the zip to a different folder location.

The problem is that now my new SDK manager installation is not opening at all. I can go through the whole login, terms and automatic/manual update set up, but after that, the below pop-up error is being presented on the SDK download screen:

lZ1LZGk.png (397×483) (imgur.com)

If I click the Yes button, it closes the SDK manager. If I click No or Cancel, then it's as if the SDK manager was not communicating to VSCode again and I'm still not able to send data to the simulator. I think my SDK manager might have been with some kind of problem for a while and that is making VSCode not communicate correctly with it.

How can I completely remove SDK manager from my computer to really start from scratch and get rid of this error? Is there some kind of registry entry that also needs to be removed?

Thanks!

Felipe
Parents
  • over 3 years ago in reply to Felipe

    , just wanted to give you a quick update. I've set up a VM with a fresh windows install, and with that the VS Code works well and I'm able to run it on the simulator with no issues. I'm now assuming that eclipse might have caused issues there (since at some point I had both installed at the same time, but not anymore), we just need to figure out how to correct that.

    However, there's one thing that is still throwing me an error: The SDK 4.0.1 download. I have that exact same error code 50332052 on the VM and all the test that I did were on the SDK 3.2.5.

Comment
  • over 3 years ago in reply to Felipe

    , just wanted to give you a quick update. I've set up a VM with a fresh windows install, and with that the VS Code works well and I'm able to run it on the simulator with no issues. I'm now assuming that eclipse might have caused issues there (since at some point I had both installed at the same time, but not anymore), we just need to figure out how to correct that.

    However, there's one thing that is still throwing me an error: The SDK 4.0.1 download. I have that exact same error code 50332052 on the VM and all the test that I did were on the SDK 3.2.5.

Children
  • over 3 years ago in reply to Travis.ConnectIQ

    I can't thank you enough for trying to help me,

    Yes, I am in Ireland indeed and the only 2 SDKs that I can't download are 4.0.0 Preview 1 and 4.0.1. They even both show their sizes as 0.0Mb on the SDK manager before trying to download, while others show sizes between 40-50Mb;

    Regarding the simulator issue, ever since I excluded the %TEMP%\Garmin\Apps folder, this is what I've been getting on the simulator:

    Basically nothing... Even though the folder inside temp gets recreated, nothing ever comes up on the simulator.

    As you requested, I excluded the files inside the bin folder of the project, then built the project again on VSCode and they were indeed recreated. However, when I run the simulator I still get the same Garmin triangle and when looking inside the %TEMP%\Garmin\Apps folder, there is no PRG file created there.

    I did the same process on the VM and was able to find the PRG file created in the corresponding folder, hence why it runs well. I'm also not sure what to do next to make VSCode create the PRG file for the simulator Disappointed

  • over 3 years ago in reply to Felipe

    The SDK manager doesn't put anything in the registry as far as I understand, so I can't imagine that some garbage in the registry is the source of your problems. I don't even think it writes any data to your user folder. It should be dumping everything into %APPDATA%\Garmin\ConnectIQ. 

    If you are able to get any of the SDK downloads other than 4.0.1, then it is quite possible there is some sort of caching issue on the server side. I was able to download the 4.0.1 SDK just now without any problems, but I'm in the US and it appears that you are in Ireland.

    As for the original problem of the simulator not seeming to pick up your changes, there are several potential points of failure. Some things that we could check...

    1. delete the files (.prg, .prg.debug.xml, and any other generated files) in the project bin folder
    2. re-build your app
    3. verify the files are re-created in the bin folder
    4. run your app in the simulator
    5. verify the timestamp on the .prg in the bin folder is approximately the same as that of the .prg in the %TEMP%\Garmin\Apps folder

    Of course this could be caused by user error, so it wouldn't hurt to double-check that also... make sure that you aren't making changes to files in one location and building the source in another.

    Other than that, I'm kinda running out of stuff to try.