Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-19750] TiSDK 4.1 Example App doesn't run with Visual Studio 2015 Community on Windows 10...

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionInvalid
Resolution Date2015-12-16T15:46:59.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsWindows
LabelsMobile, Windows, ipass1
ReporterHenry David Spells III
AssigneeChristopher Williams
Created2015-08-05T23:07:55.000+0000
Updated2017-03-30T01:05:30.000+0000

Description

I'm trying to get the Ti SDK 4.1 Example App and eventually my app built under Windows 10 I have Appcelerator Studio, build: 4.1.1.201507141126 installed on Windows 10 Pro (released) No appcelerator updates were found OS Name Microsoft Windows 10 Pro Version 10.0.10240 Build 10240 The Windows, Android and Mobile Web SDKs are installed I have Visual Studio 2015 Community version 14.0.23107.0 D14REL installed When I run the Windows Phone Developer Power Tools 8.1 I can connect to an emulator I have "Debug" selected in the "Run/Debug/Profile/Test/Package" dropdown I have tried selecting several of the windows mobile emulators including "Emulator 8.1 1080P 5.5 inch" and "Emulator 10.0.10240.0 720p 5 inch 1 GB" from the target drop down list. When I click on the green "Debug" button absolutely nothing happens in the console window even if the emulator is already launched from the Power Tools I noticed that node 0.12.2 was installed already so I installed nvmw and node v0.10.13 which is working properly on my Mac. However the problem still persists. I click on the "Debug" button and nothing happens. When I run app run -p windows -C "Emulator 8.1 1080P 6 inch" I do get some output. I get an error that says CMake error at CMakeLists.txt:15 (project): A windows Phone component with CMake requires both the Windows Desktop SDK as well as the Windows Phone "8.1" SDK. Please make sure that you have both installed. Since I have Visual Studio Community 2015 Version 14.0.23107.0 D14REL (release version) installed I believe that the SDKs must be there and Appcelerator Studio just doesn't know where to find them. I have the Windows SDK Home: preference set to "C:\Program Files (x86)\Microsoft SDKs" which is what I assume it should be so I'm not sure what to try next.

Comments

  1. Henry David Spells III 2015-08-10

    I tried switching the Windows SDK Home to be C:\Program Files (x86)\Microsoft Visual Studio 14.0 I tried running the "Employee Directory" app Here is the output from the console. Any acknowledgement at this point would be helpful. Is this just not working with the new tools? Is this specific to my machine? Am I just pointing to the wrong SDK? I've tried to point to several locations for the Windows SDK Home and no one has responded that it is correct / incorrect for Windows 10 / The current tools. Appcelerator Command-Line Interface, version 4.1.2 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. TRACE | __command__ search paths: [ "C:\\Users\\dspells\\.appcelerator\\install\\4.1.2\\package", "C:\\Users\\dspells\\.appcelerator\\install\\4.1.2\\package\\node_modules", "C:\\WINDOWS\\system32\\node_modules", "C:\\WINDOWS\\node_modules", "C:\\node_modules", "C:\\Users\\dspells\\.appcelerator\\.npm\\lib\\node_modules" ] DEBUG | [PLUGIN-LOAD] 0ms C:\Users\dspells\.appcelerator\install\4.1.2\package\appc.js DEBUG | [PLUGIN-LOAD] 536ms C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\appc-cli-titanium\appc.js DEBUG | [PLUGIN-LOAD] 0ms C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\arrow\appc.js log level set to "trace" executing command "run" set environment to {"registry":"https://software.appcelerator.com","security":"https://security.appcelerator.com","baseurl":"https://platform.appcelerator.com"} checking credentials for existing session Attempting to load session info from config file check if session is invalidated session expiry 1439318553796 false Arrow Cloud config file: C:\Users\dspells\.acs found Arrow Cloud login { mid: '2d4bca5bfbdceb7db1cabf21cd1aafe07d69b4fd', publishPort: 443, publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', username: 'dspells@me.com', cookie: [ 'connect.sid=s%3AcglAcxQGl6OCSmemQV9IkKu7.z8jd0bDgEY7%2F4K6MkjvSG9pqhJ6l4OyioeemQK88wJM; Path=/; Expires=Tue, 11 Aug 2015 18:42:35 GMT; HttpOnly' ], defaultEP: { publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', publishPort: 443 } } , checking nodeACSEndpoint= https://admin.cloudapp-enterprise.appcelerator.com Arrow Cloud cookie expiry [ 1439318555000 ] session already loaded in opts.session getCredentials() session: { "ipaddress": "169.254.80.80", "username": "dspells@me.com", "password": "", "session": "", "nonce": "", "environment": { "name": "production", "isProduction": true, "acsBaseUrl": "https://api.cloud.appcelerator.com", "acsAuthBaseUrl": "https://secure-identity.cloud.appcelerator.com", "nodeACSEndpoint": "https://admin.cloudapp-enterprise.appcelerator.com" }, "token": "", "fingerprint": "2d4bca5bfbdceb7db1cabf21cd1aafe07d69b4fd", "fingerprint_description": "Windows Machine ID: 0e1eb619-5a37-462e-b5bb-31f1c7ceaca8", "org_id": 100001535, "expiry": 1439318553796 } loading plugins for command "run" run search paths: [ "C:\\Users\\dspells\\.appcelerator\\install\\4.1.2\\package", "C:\\Users\\dspells\\.appcelerator\\install\\4.1.2\\package\\node_modules", "C:\\WINDOWS\\system32\\node_modules", "C:\\WINDOWS\\node_modules", "C:\\node_modules", "C:\\Users\\dspells\\.appcelerator\\.npm\\lib\\node_modules" ] [PLUGIN-LOAD] 0ms C:\Users\dspells\.appcelerator\install\4.1.2\package\appc.js [PLUGIN-LOAD] 250ms C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\appc-cli-titanium\appc.js run plugin: C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\appc-cli-titanium [PLUGIN-LOAD] 0ms C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\arrow\appc.js run plugin: C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\arrow plugin "arrow" failed its "when" function check, skipping... loading plugin "titanium" for command "run" CLI options via function loading plugin "titanium" for command "run" CLI options via array Duplicate option "colors" for command "run", removing... executing command "run" with the following plugins: ["titanium"] TRACE | Attempting to load session info from config file TRACE | check if session is invalidated TRACE | session expiry 1439318553796 false TRACE | session already loaded in opts.session DEBUG | Titanium Downloads Last Checked: 1439160595346 TRACE | "C:\Program Files\nodejs\node.exe" "C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\appc-cli-titanium\node_modules\titanium\bin\titanium" config -o json-object TRACE | "C:\Program Files\nodejs\node.exe" "C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\appc-cli-titanium\node_modules\titanium\bin\titanium" sdk -o json TRACE | checking for titanium, result: { activeSDK: '4.1.0.GA', defaultInstallLocation: 'C:\\ProgramData\\Titanium', installLocations: [ 'C:\\ProgramData\\Titanium', 'C:\\Users\\dspells\\AppData\\Roaming\\Titanium', 'C:\\ProgramData\\Application Data\\Titanium' ], installed: { '4.1.0.GA': 'C:\\ProgramData\\Titanium\\mobilesdk\\win32\\4.1.0.GA' } } TRACE | C:\Program Files\nodejs\node.exe [ 'C:\\Users\\dspells\\.appcelerator\\install\\4.1.2\\package\\node_modules\\appc-cli-titanium\\node_modules\\titanium\\bin\\titanium', 'build', '--platform', 'windows', '--log-level', 'trace', '--sdk', '4.1.0.GA', '--project-dir', 'C:\\Users\\dspells\\Documents\\Appcelerator_Studio_Workspace\\Employee Directory', '--target', 'wp-emulator', '--deploy-type', 'development', '--device-id', '8-1-9', '--wp-publisher-guid', '7bf82bbc-b403-4d1b-bc32-6bbe68272684', '--skip-js-minify', '--skip-js-minify', '--no-colors', '--no-progress-bars', '--no-prompt', '--prompt-type', 'socket-bundle', '--prompt-port', '49970', '--username', 'dspells@me.com', '--password', '[HIDDEN]', '--plugin-paths', 'C:\\Users\\dspells\\.appcelerator\\install\\4.1.2\\package\\node_modules', '--config-file', 'C:\\Users\\dspells\\AppData\\Local\\Temp\\build-1439233169596.json', '--no-banner' ] Mon Aug 10 2015 13:59:36 GMT-0500 (Central Daylight Time) Operating System Name = Microsoft Windows 10 Pro Version = 10.0.10240 Architecture = 64bit # CPUs = 8 Memory = 8569286656 Node.js Node.js Version = 0.10.13 npm Version = 1.3.2 Titanium CLI CLI Version = 4.0.1 Titanium SDK SDK Version = 4.1.0.GA SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\4.1.0.GA Target Platform = windows Command C:\Users\dspells\AppData\Roaming\nvm\v0.10.13\node.exe C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\appc-cli-titanium\node_modules\titanium\bin\titanium build --platform windows --log-level trace --sdk 4.1.0.GA --project-dir C:\Users\dspells\Documents\Appcelerator_Studio_Workspace\Employee Directory --target wp-emulator --deploy-type development --device-id 8-1-9 --wp-publisher-guid 7bf82bbc-b403-4d1b-bc32-6bbe68272684 --skip-js-minify --skip-js-minify --no-colors --no-progress-bars --no-prompt --prompt-type socket-bundle --prompt-port 49970 --username dspells@me.com --password tchrist --plugin-paths C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules --config-file C:\Users\dspells\AppData\Local\Temp\build-1439233169596.json --no-banner [INFO] : Found Titanium plugin id=ti.alloy version=1.0 [INFO] : Building for Windows Phone emulator: 8-1-9 [INFO] : Deploy type: development [INFO] : Debugging disabled [INFO] : Profiler disabled [INFO] : Forcing rebuild: C:\Users\dspells\AppData\Local\Temp\Employee Directory\build-manifest.json does not exist [INFO] : Found Alloy app in C:\Users\dspells\Documents\Appcelerator_Studio_Workspace\Employee Directory\app [INFO] : Executing Alloy compile: cmd /s /c C:\Users\dspells\.appcelerator\install\4.1.2\package\node_modules\appc-cli-titanium\node_modules\.bin\alloy compile C:\Users\dspells\Documents\Appcelerator_Studio_Workspace\Employee Directory\app --config platform=windows,version=0,simtype=none,devicefamily=none,deploytype=development,target=wp-emulator --no-colors .__ .__ _____ | | | | ____ ___.__. \__ \ | | | | / _ < | | / __ \| |_| |_( <_> )___ | (____ /____/____/\____// ____| \/ \/ [WARN] is only available in Android Alloy 1.6.2 by Appcelerator. The MVC app framework for Titanium. [WARN] To get rid of this warning, add platform="android" to your element [INFO] [config.json] config.json unchanged, using cached config.json... [INFO] ----- MVC GENERATION ----- [INFO] [global style] loading from cache... [INFO] [annotation.xml] view processing... [INFO] style: "annotation.tss" [INFO] view: "annotation.xml" [INFO] controller: "annotation.js" [INFO] created: "Resources\windows\alloy\controllers\annotation.js" [INFO] created: "Resources\windows\alloy\styles\annotation.js" [INFO] [directory.xml] view processing... [INFO] style: "directory.tss" [INFO] view: "directory.xml" [INFO] controller: "directory.js" [INFO] created: "Resources\windows\alloy\controllers\directory.js" [INFO] created: "Resources\windows\alloy\styles\directory.js" [INFO] [index.xml] view processing... [INFO] style: "index.tss" [INFO] view: "index.xml" [INFO] controller: "index.js" [INFO] created: "Resources\windows\alloy\controllers\index.js" [INFO] created: "Resources\windows\alloy\styles\index.js" [INFO] [loader.xml] view processing... [INFO] style: "loader.tss" [INFO] view: "loader.xml" [INFO] controller: "loader.js" [INFO] created: "Resources\windows\alloy\controllers\loader.js" [INFO] created: "Resources\windows\alloy\styles\loader.js" [INFO] [profile.xml] view processing... [INFO] style: "profile.tss" [INFO] view: "profile.xml" [INFO] controller: "profile.js" [INFO] created: "Resources\windows\alloy\controllers\profile.js" [INFO] created: "Resources\windows\alloy\styles\profile.js" [INFO] [INFO] [app.js] using cached app.js... [INFO] [INFO] ----- OPTIMIZING ----- [INFO] - alloy\CFG.js [INFO] - windows\alloy.js [INFO] - windows\favoritesmgr.js [INFO] - windows\alloy\sync\localStorage.js [INFO] - windows\alloy\sync\properties.js [INFO] - windows\alloy\sync\sql.js [INFO] [INFO] Alloy compiled in 1.02792s [INFO] : Alloy compiler completed successfully [INFO] : Launching emulator: 8-1-9 [INFO] : Processing JavaScript files [INFO] : Generating i18n files [INFO] : Generating Native Type Wrappers [INFO] : Generating stubs for: Platform.Object [INFO] : Setting up native modules for CMakeLists.txt... [INFO] : Writing appxmanifest C:\Users\dspells\AppData\Local\Temp\Employee Directory\Package.store.appxmanifest.in [INFO] : Writing appxmanifest C:\Users\dspells\AppData\Local\Temp\Employee Directory\Package.phone.appxmanifest.in [INFO] : Writing CMakeLists.txt: C:\Users\dspells\AppData\Local\Temp\Employee Directory\CMakeLists.txt [INFO] : Running cmake at C:\ProgramData\Titanium\mobilesdk\win32\4.1.0.GA\windows\cli\vendor\cmake\bin\cmake.exe in directory C:\Users\dspells\AppData\Local\Temp\Employee Directory\phone.x86 [INFO] : Windows Phone emulator is ready [WARN] : CMake Error at CMakeLists.txt:15 (project): [INFO] : -- Configuring incomplete, errors occurred! See also "C:/Users/dspells/AppData/Local/Temp/Employee Directory/phone.x86/CMakeFiles/CMakeOutput.log". A Windows Phone component with CMake requires both the Windows Desktop SDK as well as the Windows Phone '8.1' SDK. Please make sure that you have both installed TRACE | titanium exited with exit code 1
  2. Christopher Williams 2015-08-18

    We have not yet certified or officially support Windows 10 or Visual Studio 2015 (which were released not too long ago). We support Windows 8.1 and Visual Studio 2013 officially. According to the error message it seems likely that you do not the have the Windows 8.1 Phone and Store/Desktop SDKs installed. Since you're using VS2015 and Windows 10, it's likely that it has Win 10 SDKs installed, not 8.1.
  3. Kai Lu 2015-08-18

    Hi Chris, Thank you for you reply. What you said makes sense to me but do you have the plan to support win 10 in the near future? We'd love to use the latest and greatest operating system and development tools to work on our projects. If there is a work around for now we would also happily accept it.
  4. Christopher Williams 2015-08-18

    Looks like this likely related to VS2015 and CMake incompatibility. I believe that we use a generator string of "Visual Studio 12 2013", which choose VS2013 toolchain. Ultimately, CMake then uses the code here to search for the SDKs: https://github.com/Kitware/CMake/blob/master/Source/cmGlobalVisualStudio12Generator.cxx#L219 My guess is that the search for the Windows Desktop SDK fails, because the toolchain version changed from 12.0 to 14.0: 
       "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\"
       "VisualStudio\\12.0\\VC\\LibraryDesktop";
    So it seems to me, we may need to work around the issue in our CLI by detecting which VS version is installed and using that to change the generator string we use ("Visual Studio 14 2015" vs "Visual Studio 12 2013").
  5. Christopher Williams 2015-08-18

    If you're using VS 2015, please try installing the Windows Phone 8.1 SDK as well. It should be here: https://www.microsoft.com/en-us/download/details.aspx?id=43719 That may fix the issue.
  6. Kai Lu 2015-08-18

    Hi Chris, I've already tried installing the windows phone 8.1 SDK but it didn't work. Maybe it's the generator string issue you mentioned earlier. Hope it's going to be fixed soon.
  7. Henry David Spells III 2015-08-19

    I tried running this "https://www.microsoft.com/en-us/download/details.aspx?id=43719" and it did update the number of emulators on the list but it still gets the same CMake error. BTW: Please tell me where the official Windows SDK Home preference should be set? Is it "C:\Program Files (x86)\Microsoft SDKs" or "C:\Program Files (x86)\Microsoft Visual Studio 14.0"? Also, if I uninstall VS 2015 Community and install VS 2013 Community should it work?
  8. Fokke Zandbergen 2015-08-25

  9. Kota Iguchi 2015-10-21

    For VS 2015 support, my understanding is that Windows Phone 8.1 SDK is only installed with VS 2013, so in order to develop Windows Phone 8.1 app you actually need to install VS 2013 (with Windows Phone SDK) too, even when you prefer to use VS 2015. https://dev.windows.com/en-us/develop/download-phone-sdk
  10. Kota Iguchi 2015-10-21

    FYI I experienced that upgrading Windows 8.1 to Windows 10 broke my Visual Studio installation. At the time my Visual Studio was not able to create new Windows Phone project, and I ended up cleaning everything and re-install Windows 10...
  11. Christopher Williams 2015-10-22

    [~fokkezb] Until 5.1.0 SDK, we do not support anything other than Windows 8.1 and Visual Studio 2013 officially. Kota's made some changes to support Windows 10 and VS 2015 for building Windows 8.1 apps in the 5.1.0 stream.
  12. Fokke Zandbergen 2015-10-26

    We might want to clarify http://docs.appcelerator.com/platform/latest/#!/guide/Installing_the_Windows_Phone_SDK-section-43306274_InstallingtheWindowsPhoneSDK-VisualStudio which could be read as Visual Studio 2015 being "higher" then VS2013 Community as well.
  13. Kota Iguchi 2015-10-26

    ok [~fokkezb], created ticket for it. [~gmathews], Could you look into TIMOB-19789? I think our documentation is little bit obsolete, we want to add documentation about Visual Studio 2015 and Windows 10 support.
  14. Christopher Williams 2015-12-16

    Until the 5.1.0 release we did not officially support use of Visual Studio 2015 for windows apps. Now that we do, you still must install the Windows 8.1 SDK and Windows Phone 8.1 SDK and emulators to be able to build (as we still target 8.1). As of 6.0.0 we should officially support Windows (Phone and Desktop) 8.1 _and_ 10.0 as build targets. We have preliminary support for 10.0 in the upcoming 5.2.0 release, but I'd still say wit was "unofficially supported" until 6.0.
  15. Henry David Spells III 2015-12-16

    Thanks for the update on the issue. Since this bug is no longer being tracked can you point me to a tracking item in the database that I can watch concerning support for using Appcelerator on Windows 10?
  16. Christopher Williams 2015-12-17

  17. Henry David Spells III 2015-12-17

    This epic appears to be for Windows 10 mobile. I just want to be able to run appcelerator on and Windows 10 machine. Are these problems tied together?
  18. Kota Iguchi 2017-03-30

    Closing this, as I believe this ticket is obsolete. [~lmorris] Thanks for the heads up.

JSON Source