Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-9023] iOS Simulator: dirty project does not rebuild on deployment

GitHub Issuen/a
TypeBug
PriorityLow
StatusClosed
ResolutionCannot Reproduce
Resolution Date2016-08-24T18:14:54.000+0000
Affected Version/sRelease 2.0.2, Release 2.0.1, Release 3.0.0
Fix Version/sn/a
ComponentsCLI
Labelscore, qe-ios040912, qe-ios100112
ReporterDustin Hyde
AssigneeEric Merriman
Created2012-03-29T14:01:43.000+0000
Updated2017-03-24T21:58:07.000+0000

Description

Studio projects with filesystem changes do not rebuild on simulator deployment. This is an edge case where files are added or removed from project sub-directories. Attaching a project containing a module to demonstrate behavior. This issue is not new. Steps to Reproduce: 1. Run attached project in iOS simulator. 2. Change '_modules' folder to 'modules'. This should cause a proper module include. 3. Re-run simulator. Expected Result: Module should load, app should work. Actual Result: Module fails to load. App only works on project clean and re-deploy.

Attachments

FileDateSize
NewProject.zip2012-03-29T14:01:44.000+00009764129

Comments

  1. Dustin Hyde 2012-12-12

    Escalating ticket. Updated environment info.
  2. Paras Mishra 2014-07-03

    Run the attached app, redeployed the app again without cleaning on simulator, app works fine Environment used: Device : iOS simulator 7.1 SDK: 3.3.0.v20140625133319 CLI version : 3.3.0-rc4 OS : MAC OSX 10.9.2 Alloy: 1.4.0-rc3 ACS: 1.0.14 npm:1.3.2 LiveView: 1.0.4 Appcelerator Studio, build: 3.3.0.201406271159 titanium-code-processor: 1.1.1 XCode : 5.1.1
  3. Chris Barber 2016-08-24

    This ticket is basically saying that subsequent builds don't properly recover from a previously failed build due to missing ti modules. I tested with Titanium SDK master (6.1.0) and works just fine. I'm not sure exactly which version of Titanium SDK this was fixed. Titanium 5.0.0 had improved iOS builds, so certainly by then.
  4. Lee Morris 2017-03-24

    Closing ticket as the issue cannot be reproduced and with reference to the previous comments.

JSON Source