Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-9198] iOS: non-existent embedded require causes crash

GitHub Issuen/a
TypeBug
PriorityLow
StatusClosed
ResolutionWon't Do
Resolution Date2020-01-10T18:07:53.000+0000
Affected Version/sRelease 2.0.0, Release 2.0.2, Release 2.0.1, Release 3.1.0
Fix Version/sn/a
ComponentsiOS
Labelscore, parity, qe-ios050912
ReporterDustin Hyde
AssigneeUnknown
Created2012-05-22T18:26:01.000+0000
Updated2020-01-10T18:07:53.000+0000

Description

When a CommonJS require within a CommonJS require does not reference an existing file the app will crash. However, when a first-level CommonJS require does not reference an existing file, there will be an exception (expected). This is not a regression. This is a parity issue as it does not affect Android (Emulator 2.2). Files Attached: Studio Console Log, Xcode Console Log, Device Crash Log, Expected Screenshot Steps to Reproduce: 1. Create a new app with the following files: app.js
require('other');
other.js
require('non-existent_file');
2. Run app. Expected Result: App should run without crashing. A runtime exception should appear. Actual Result: App crashes on load.

Attachments

FileDateSize
expected.png2012-05-22T18:26:01.000+0000136979
MyCrash_2012-05-22-180843_iPhone-4s-Verizon.crash2012-05-22T18:26:01.000+000027200
studio_console_log.txt2012-05-22T18:26:01.000+0000630
xcode_console_log.txt2012-05-22T18:26:01.000+00005987

Comments

  1. jithinpv 2013-04-12

    Issue reproduces Tested with Titanium Studio, build: 3.0.1.201212181159 Titanium SDK version: 3.1.0 Titanium SDK version: 3.0.2 iOS iPhone Simulator: iOS SDK version: 6.0
  2. Fokke Zandbergen 2015-06-02

    This is still true in 4.0.0.GA and annoying when working with LiveView when you make a typo or add a require before adding the CommonJS itself and it crashes, requiring a new build.
  3. Alan Hutton 2020-01-10

    This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.

JSON Source