App Settings Editor not working in Simulator?

Former Member
Former Member
Hello.

Am I missing something? When I compile my apps with SDK 2.2.x, I can use the App Settings Editor and I see the changes reflected in my apps.

However, with 2.3.x and 2.4.1, the settings do nothing. Has something changed since 2.2.x?

I have run into trouble because the Store now longer accepts uploaded apps compiled with 2.2.x.

Thanks.
  • You shouldn't need to create a new user profile. You could make a C:\Temp folder and update your environment variables TEMP and TMP to point to that directory and everything should work.

    While trying to reproduce this on my Windows 7 machine, I found that if I entered a path with whitespace in the TEMP environment variable in the Environment Settings section of the control panel, when I printed the value of the variables at the command prompt, windows was automatically using short path names. i.e., If I set the value to C:\Users\vitek\AppData\Local\Temp\A B, this is what I was shown at the command prompt...

    C:\Users\vitek>echo %TEMP%
    C:\Users\vitek\AppData\Local\Temp\AB2B67~1

    C:\Users\vitek>


    If I set the environment variable from the command prompt directly, then the path would contain a space and I was able to reproduce the problem.

    C:\Users\vitek>set TEMP=C:\Users\vitek\AppData\Local\Temp\A B

    C:\Users\vitek>echo %TEMP%
    C:\Users\vitek\AppData\Local\Temp\A B

    C:\Users\vitek>


    So it looks like windows somehow has safeguards in place to protect users from this, but for some reason those safe-guards aren't working for you? In my investigation, I found a problem that was older than the 2.2.x release time frame, so I'm not exactly sure how this is showing up for you with one SDK and not the other.

    Travis
  • Former Member
    Former Member
    Thank you, Travis. I'm not sure, but I had no problems with SDK 2.2.x, but did with 2.3.x onwards. Maybe Windows 10 is slightly different in this regard somehow?
  • Former Member
    Former Member
    Wonderful! Manually setting %TMP% and %TEMP% to C:\TEMP fixed the issue for me! Thanks, Travis!
  • Thank you, Travis. I'm not sure, but I had no problems with SDK 2.2.x, but did with 2.3.x onwards. Maybe Windows 10 is slightly different in this regard somehow?


    I'm not sure. I found and fixed an issue that should resolve this particular problem. I intend to spend a some time trying to find additional problems with unusual path names. Hopefully I'll get them all stamped out.
  • Former Member
    Former Member
    Many thanks, Travis. :-)
  • Former Member
    Former Member
    This has been fixed in version 2.4.2. Please let us know if you have any further questions on this.