Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-18347] Alloy projects open, then immediately close on Windows Phone emulator

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2015-01-28T16:36:20.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsWindows
Labelsn/a
ReporterTim Poulsen
AssigneeMatt Langston
Created2015-01-08T21:55:59.000+0000
Updated2017-03-24T21:04:31.000+0000

Description

I can build and run a two-tabbed default classic project (created with ti new) just fine. However, I cannot run a stock default new alloy project. It builds, opens, and immediately closes. After just a brief moment, the build script ends and returns to the prompt with the following: 
[INFO]  Writing build manifest: C:\Users\Tim\AppData\Local\Temp\ALOY1180\build-manifest.json
[INFO]  Copying results back to project build directory
[INFO]  Finished building the application in 18s 663ms
[INFO]  Finished building the application in 19s 710ms
[INFO]  Installing and launching the application
[INFO]  Project built successfully in 19s 710ms

[ERROR] The remote procedure call failed.
(With a classic app, the build command doesn't exits and I continue to get log output from the emulator.) I can’t open the app from the emulator’s app screen either — again, it opens and immediately closes. I have tried simplifying the app to simply one label in a window with no styling applied and get the same results. 
<Alloy>
   <Window class="container">
      <Label id="label">Hello, World</Label>
   </Window>
</Alloy>
FYI, to install the Windows branch of Alloy, use: npm install -g git://github.com/appcelerator/alloy.git#windows

Attachments

FileDateSize
Assets.zip2015-01-09T14:47:24.000+0000110026
Screen Shot 2015-01-09 at 9.40.57 AM.png2015-01-09T14:42:05.000+000019070

Comments

  1. Christopher Williams 2015-01-09

    After trying to build, I see the same result as Tim. I then opened the sln file in VS 2013 U4 and tried to debug on emulator and eventually hit an uncaught exception stemming from HAL. (There are three caught exceptions stemming from the logger trying to connect to the CLI, then we see the uncaught HAL exceptions)
  2. Matthew Watson 2015-01-20

    Non alloy projects also have the same issue.
  3. Christopher Williams 2015-01-20

    [~pl4gu3b0rn] There's an intermittent issue where apps close immediately on simulator, but can be opened by manually launching them (clicking through the emulator). This issue is specific to our handling of the underscore.js require used by alloy and prevents alloy apps from ever launching.
  4. Matthew Watson 2015-01-21

    Ah well my application im testing with is not alloy. And this also shows the same log output when launched from the cli. And always closes after the splash screen is displayed. Opening them again after it has closed will either do the same again, or just show a black screen. Totally new to windows phone development here, is there any useful log output I can get to to try and work out where its failing? I have tried opening up the solution file in visual studio and running it there, but I get deployment errors.
  5. Christopher Williams 2015-01-28

    The original issue for alloy _appears_ to be fixed now. There are other bugs tangentially related to alloy that need to be fixed that I've found (TIMOB-18347).
  6. Tim Poulsen 2015-01-28

    I concur. I can build and run an Alloy app on the Windows Phone emulator using the most recent SDK master and the changes in TIMOB-18457.
  7. Lee Morris 2017-03-24

    Closing ticket as fixed with reference to previous comments.

JSON Source