I am trying to run an Android app made in Titanium Appcelerator, to run in Windows Phone emulator
I have VS 2013 Pro & Appcelerator Studio 4.5
I wish to run app in Windows Phone emulator, but it gives me error
[ERROR] : Invalid "--device-id" value "8-1-1"
For help, run: titanium.js help build
Command Details
Operating System
Name = Microsoft Windows 10 Pro
Version = 10.0.10586
Architecture = 32bit
# CPUs = 4
Memory = 8479367168
Node.js
Node.js Version = 0.12.7
npm Version = 2.11.3
Titanium CLI
CLI Version = 5.0.6
Titanium SDK
SDK Version = 5.2.2.GA
SDK Path = C:\ProgramData\Titanium\mobilesdk\win32\5.2.2.GA
Target Platform = windows
Command
c:\Program Files (x86)\nodejs\node.exe c:\Users\Test\.appcelerator\install\5.2.2\package\node_modules\titanium\lib\titanium.js build run -p windows -T ws-local --wp-sdk 10 --config-file C:\Users\Test\AppData\Loca
l\Temp\build-1462961770428.json --log-level info --no-banner --project-dir c:\Users\Test\Documents\Appcelerator_Studio_Workspace\TestProject
Also, On running :
appc run -p windows -T ws-local --wp-sdk 8.1
I get :
What pfx file should sign the app? (leave blank to generate):
What will be your PFX password?:
Both of which I bypass with enter key.
Then I get a prompt to "Enter a Private Key Password" with "Key" as "Subject Key". Entering anything here gives
[ERROR] An error occurred during build after 4m 29s 170ms
[ERROR] Failed to create certificate (code 4294967295)
Also running :
appc run -p windows --target wp-emulator --deploy-time development --device-id 8-1-1
Gives :
2016-05-11T10:25:57.544Z | ERROR | An uncaught exception was thrown!
No Windows Phone emulators found
2016-05-11T10:25:57.562Z | ERROR | No Windows Phone emulators found
Even though i have installed Windows Phone 8.1 Emulators
I have tried literally every possible solution...
Please help to run emulator
Make sure windows phone sdk is installed and its path is added in studio. Make sure sdk and emulators are detected by studio. Add windows app publisher id also.Run command
In my system I get the following output in windows section.
If you find everything ok in your system try running the following command.