App Settings Editor not working in Simulator?

Hmmm...that's really strange. I went through those steps exactly. Did you by chance set a hard path to an older SDK in you system PATH? I'm thinking for some reason it's pushing the old sim and it's struggling to handle the new plugin and calls or something along those lines. Another thing to note is that even when you uninstall Eclipses it keeps some preferences saved in a ".p2" folder in your user directory (i.e. - C:\Users\Coleman\.p2). There is also a ".eclipse" folder there that could be holding some configurations that are throwing the sim off as well. Let me know what you find.

Thanks,
-Coleman

Hi Coleman.

Thanks for spending time doing that! Great suggestions. I will check the path when I get home. When I first installed the SDK, I did do it manually, rather than using the SDK manager (which I discovered later). I will post back my results. Many thanks.

Update:

I have:
* checked the path for the system and also for my user. Nothing there.
* deleted all installs of Eclipse
* deleted my workspace folder.
* deleted my .p2 folder and my .eclipse folder.
* deleted my GARMIN folder in %temp%.
* Installed a fresh copy of Eclipse Oxygen
* Added the Garmin repos and installed the ConnectIQ plugin and SDK Manager
* Pointed the plugin to my developer key.
* Installed SDK 2.4.1 via the SDK manager.
* Opened the "Simple with Settings" project I created yesterday.
* Ran it.
* Changed settings.
* Nothing happens in the simulator.
* Nothing in the appBase in the simulator (i.e. CTRL-O in the Simulator).

:-(

Could it be because I have a space in my home folder, i.e. c:\users\firstname lastname\ ?

The GARMIN folder in %temp% would be affected, and maybe the App Settings Editor cannot write there, or maybe the Simulator cannot read the appBase file stored in there? Whereas with SDK 2.2.x, it could?

For what it's worth, I experienced some issues running the Simulator in the past on Mac OS X (errors were displayed in the Eclipse and the Simulator window wouldn't launch) that was resolved immediately once I removed a space in the path to my source code. I don't remember all of my details and unfortunately I don't think I had enough information to submit a bug report.

Could it be because I have a space in my home folder, i.e. c:\users\firstname lastname\ ?

The GARMIN folder in %temp% would be affected, and maybe the App Settings Editor cannot write there, or maybe the Simulator cannot read the appBase file stored in there? Whereas with SDK 2.2.x, it could?

There have been issues with spaces (in project names) before so that's certainly a possibility that a space in a username could also have an unwanted effect....

do you have the possibility to create another (local) user on your pc to see if you also have the issue with a username without spaces?

Yes, I found out about the problem with spaces in the projects folder path early on. Creating a new user account is the next step. Thanks guys. I will keep you updated.

SOLVED:

UPDATE: Set environment variables TMP and TEMP for the user to a folder with no spaces in the path i.e. C:\TEMP. See Below.


I created a new local user account with no spaces in the user name, i.e. no space in the home folder.
I went through all the same steps, and everything works!

The problem does NOT exist in SDK 2.2.7, so I am presuming a bug was introduced with SDK 2.3.x as it affects this and 2.4.1.

This will be annoying having to log in as a different user to use Eclipse, so hopefully Garmin can sort this with the next SDK.

Thanks everyone!

Hey grolschie,

Thank you so much for finding this. We had some bugs in pathing when spaces were used, but thought they were fixed. It's not a normal test that we run after it was fixed so it's possible that there was a regression. However, I think that it is more likely that there is something unique to your case here. Either way, I've got a ticket created to address this and we will take a look.

Thanks,
-Coleman

Thank you so much, Coleman!

Previously, I had to switch to 2.2.x from 2.3.x to test things. I only came unstuck recently when I tried to update my watchface and the website would not allow it because it was compiled with 2.2.x.