Titanium JIRA Archive
Appcelerator Community (AC)

[AC-2756] Android: UI - TabGroup activities do not fire

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionNeeds more info
Resolution Date2011-12-29T04:56:46.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsTitanium SDK & CLI
Labelsn/a
ReporterStephen Feather
AssigneePaul Dowsett
Created2011-11-28T08:14:15.000+0000
Updated2016-03-08T07:47:39.000+0000

Description

Steps to reproduce

Create a new default project.

Run project on Device.

Place phonecall to device.

Adding Activity event handlers ineffective as they don't seem to be fired before the crash.

Results

* Crash 100% of the time if you answer the call * Crash 90% of the time if you ignore the call * Crash 0% of the time if calling party terminates call before you make a decision * Crash occurs if app is sent to background using home button as well

Logs

In DDMS observe:
11-28 10:58:07.431: I/WindowManager(1316): WIN DEATH: Window{4054be78 com.stephenfeather.tabcrash/ti.modules.titanium.ui.TiTabActivity paused=false}
11-28 10:58:07.447: I/WindowManager(1316): WIN DEATH: Window{4053e108 com.stephenfeather.tabcrash/com.stephenfeather.tabcrash.TabcrashActivity paused=false}

Comments

  1. Stephen Feather 2011-11-28

    While I understand that "win death" would not be described by a programmer as a "crash" that is how the end user perceives it. This wouldn't be so much of a problem were the TabGroup activities to fire correctly so as to assist in the capture of the app state. As it is, in order to cleanly restore a the app to the place it was when a user received a call or hit home, one has to write out the current state at every occasion it changes. This is extremely high overhead.
  2. Paul Dowsett 2011-12-29

    Stephen If this report is accurate, I agree that this is a serious problem. Are there two issues here, though? ie:

    default app crashes when a phonecall is received (as per the results section)

    activities not fired for tabgroups (where is the test case for this?)

    If I am correct, then please open another ticket for the other issue. I will mark this resolved for now. I will reopen once I have fully understood the situation, and will then move it to the main project. Cheers
  3. Paul Dowsett 2012-02-17

    Closing due to inactivity. If this issue still exists, please raise a new ticket, including all the information in the [JIRA Ticket Checklist](https://wiki.appcelerator.org/display/guides/How+to+Submit+a+Bug+Report#HowtoSubmitaBugReport-JIRATicketChecklist) to ensure that we can escalate it quickly. Read [How to Submit a Bug Report](https://wiki.appcelerator.org/display/guides/How+to+Submit+a+Bug+Report) if you have not read it before, and always start a ticket using the [JIRA Ticket Template](https://wiki.appcelerator.org/display/guides/JIRA+Ticket+Template). Thanks in advance

JSON Source