[TIMOB-18316] Windows: Cannot launch app into emulator with "Failed to install app" error
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2015-01-07T16:19:21.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 4.0.0 |
| Components | Windows |
| Labels | windows-8, windows8 |
| Reporter | Leor Brenman |
| Assignee | Christopher Williams |
| Created | 2015-01-06T14:50:18.000+0000 |
| Updated | 2015-01-08T14:30:17.000+0000 |
Description
Win8 Preview, cannot launch app into emulator or device
I am following the instructions from the Blog Post (http://www.appcelerator.com/blog/2014/12/windows-platform-preview/)
When i launch to the emulator, using:
ti build -p windows -T wp-emulator -C 8-1-1 --wp-publisher-guid 00000000-0000-1000-8000-000000000000
it builds and installs the app on the emulator but exists immediately
Error message is:
[ERROR] Failed to install app (code -2146233088)
Terminal log with "ti info" and screen shot attached
Attachments
| File | Date | Size |
|---|---|---|
| Screen Shot 2015-01-06 at 9.43.00 AM.png | 2015-01-06T14:50:18.000+0000 | 3967444 |
| Screen Shot 2015-01-07 at 3.39.26 PM.png | 2015-01-07T20:44:49.000+0000 | 1791943 |
| win8_console_log.rtf | 2015-01-06T14:50:18.000+0000 | 14020 |
Note that This exact error was happening for users in the Titanium Contributors flow as well. There's a related issue open for windowslib to better surface the underlying error messages here: https://github.com/appcelerator/windowslib/issues/5 In this case, the user(s) on the Titanium Contributor flow reported that the true error message was:
Thanks Chris, is there a workaround or solution that I can try out or am i stuck?
I think I've found the issue. Basically this will happen if the DLLs fail to load as Gary states, and this is a direct result of some sort of build issue either on our building/packaging on Jenkins, or in the cmake setup we use for the user projects. In this case, I believe it was both, resulting from new modules being adding as separate libraries - specifically The "Ti" module. When a new module is added, or sometimes even when dependencies between modules change, it requires tweaks to our build to make sure we pick up the generated libs when we package up the SDK on Jenkins - and it requires tweaks to the cmake scripts to be able to reference and find the built library.
https://github.com/appcelerator/titanium_mobile_windows/pull/75
So one of the reasons why we only saw this on some people's machines was when they installed the SDK. If they installed the SDK before the new "Ti" module got in, it should have worked. But anyone who tried an SDK after that would get this failure (which is why so many of the end users are seeing this).
Thanks Chris. Is there some workaround for me? I did have older SDKs and Ti installed. I can uninstall and try to resin tall again if you think that may work?
[~lbrenman] The PR just got merged and the SDK is building. Once it's done you should be able to just do a
ti sdk install -b master -dand get the fix. You'll have to modify your existing project to use that SDK version in the tiapp.xml. Given historical build times, I'd expect the build to be done about 45 minutes from now.FYI, I just verified using the latest master build and it worked for me, so hopefully you can try now [~lbrenman].
Hi Chris, I just tried and it worked!!! Thanks for the taking care of this so quickly.
Screen shot of everything working well