[TIMOB-6494] Android: Implement activity stack behavior to address currentActivity being null
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-12-07T02:17:21.000+0000 |
| Affected Version/s | Release 1.8.0.1 |
| Fix Version/s | Sprint 2011-49, Release 1.8.0.1 |
| Components | Android |
| Labels | branch-v8, verified-1.8.0.1 |
| Reporter | Opie Cyrus |
| Assignee | Opie Cyrus |
| Created | 2011-12-06T18:00:51.000+0000 |
| Updated | 2011-12-19T16:07:36.000+0000 |
Description
When the device screen goes black, TiApplication.getCurrentActivity is set to null which causes a problem if proxies are created in this state since their activity reference will be null. The larger fix for this is to implement an activity stack representing the Titanium activities on the stack.
Requested test case.
IIRC this fix affected several others but they aren't linked here, let me try and find which ones
See the failure in TIMOB-6247: A run of the drillbit "ui" test on a phone or tablet with the screen off used to fail, but now it passes w/ this fix
Tested with Ti Mob SDK 1.8.0.1.RC3 with tests steps on TIMOB-6247 on Galaxy Tab 10.1 Verified that when the device screen is off, test still passes