| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2012-07-05T05:51:10.000+0000 |
|---|
| Affected Version/s | Release 1.7.5, Release 1.8.0.1, Release 2.0.0 |
|---|
| Fix Version/s | Release 2.1.0, Sprint 2012-09 API |
|---|
| Components | Android |
|---|
| Labels | api, module_tabgroup, parity, qe-and011912, qe-testadded |
|---|
| Reporter | Dustin Hyde |
|---|
| Assignee | Josh Roesslein |
|---|
| Created | 2012-01-19T13:29:31.000+0000 |
|---|
| Updated | 2012-07-05T10:42:32.000+0000 |
|---|
When TabGroup.open() is called when the TabGroup contains a Tab with an uninitialized window property, the app crashes. Log Attached.
Steps to Reproduce:
1. Run Code.
var tabGroup = Ti.UI.createTabGroup();
var tab = Ti.UI.createTab();
tabGroup.addTab(tab);
tabGroup.open();
Expected Result:
App should display a blank screen (as it does in iOS), or generate a runtime error.
Actual Result:
Crash.
TIMOB-7000 involves not being able to set a window property in a tab after object creation, causing a crash when tabgroup.open() is called. This issue (TIMOB-7300) addresses the initial crash behavior of TIMOB-7000 that is still prevalent.
Submitted [PR #2077](https://github.com/appcelerator/titanium_mobile/pull/2077) to resolve issue. This removes the crash seen and matchs up with iOS's fallback to displaying an empty tab.
Titanium Studio: 2.1.0.201206221045 Mobile SDK: 2.1.0.v20120622174154 OS: X Lion Device: Samsung Galaxy Runtime: V8 & Rhino Fixed. Blank screen launched. App didn't crash, successful launch.
Reopening to update labels.