Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-12779] "Packaging Error" appears in Windows while packaging project in mobile web using legacy cli

GitHub Issuen/a
TypeBug
PriorityLow
StatusClosed
ResolutionWon't Fix
Resolution Date2013-03-14T04:56:38.000+0000
Affected Version/sRelease 3.0.2
Fix Version/sn/a
ComponentsMobileWeb
Labelsqe-3.0.2, regression
ReporterPragya Rastogi
AssigneeIngo Muschenetz
Created2013-02-11T10:50:58.000+0000
Updated2013-03-14T16:20:33.000+0000

Description

Works fine on SDK: 3.0.0.GA. Hence is regression issue. Steps To Reproduce: =================== 1. Create a titanium project or alloy project. 2. Package on MobileWeb Actual: Mobile Packaging fails for titanium and Alloy project. Workaround: Works fine on clean install machine. Expected: Mobile Packaging must occur successfully on windows machine wherein installation and UN-installation is been done several times. Note: No Studio Logs or Console logs appear for same. AppId used was app.test (ie. any random appid not ti.cloud)

Attachments

FileDateSize
PackagingError.png2013-02-11T10:50:58.000+0000219408

Comments

  1. Michael Xia 2013-02-12

    ï¼ Pragya - could you do the following: 1. Open Preferences > Titanium Studio > Troubleshooting page, change Debug Level to "All" and make the com.aptana.core/debug/shell entry checked; 2. Restart Studio; 3. Run packaging on Mobile Web again to generate the error; 4. Attach the Studio log via Help > Titanium Studio > View Log File. Also you could try running the same command you see in the log from the command line to see if it returns the same error. Thanks.
  2. Dustin Hyde 2013-02-12

    This is probably an SDK regression new to SDK 3.0.2. It is showing up because we are calling the legacy script when the CLI is not detected. To reproduce this behavior you need to uninstall the CLI and package a mobileweb app in SDK 3.0.2. @Michael: Should we be using the legacy scripts at all? For instance we don't run the legacy script for mobileweb preview in browser, the operation just fails (with correct missing cli error).
  3. Michael Xia 2013-02-18

    We will address the issue with not calling the legacy script if 3.0.0+ SDK is selected and CLI is not installed in TISTUD-3474. Moving this ticket to platform as it's a 3.0.2 SDK regression.
  4. Ingo Muschenetz 2013-03-14

    To confirm, this is using the legacy scripts (i.e. the Python ones)?
  5. Dustin Hyde 2013-03-14

    Correct.
  6. Ingo Muschenetz 2013-03-14

    Okay. Those scripts are deprecated, so we won't be updating them.
  7. Dustin Hyde 2013-03-14

    Closing. Python CLI Deprecated.

JSON Source