[TIMOB-3053] Android: showCamera executes immediately (before parent activity is finished drawing)
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T02:00:47.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.6.0 M08 |
| Components | Android |
| Labels | android, camera, lifecycle_refactor, regression, release-1.6.0, reported-1.6.0 |
| Reporter | Marshall Culpepper |
| Assignee | Marshall Culpepper |
| Created | 2011-04-15T03:35:37.000+0000 |
| Updated | 2011-04-17T02:00:47.000+0000 |
Description
Caused by lifecycle refactor. We might just need to post showCamera on to the UI thread directly instead of processing it in our loop iteration. The result in the KS Camera Basic test is a deadlock or exception showing the image after the photo has been taken.
(from [a05a7df4e31e1d520c6fef81b856c3f2a32dc0b4]) start the camera activity in another job on the main thread so it doesn't get in the way of the current (if any) main thread job
finishing. kroll context threads now show their top level URL as well
for added debugging info [#3053 state:fixed-in-qa]
https://github.com/appcelerator/titanium_mobile/commit/a05a7df4e31e1d520c6fef81b856c3f2a32dc0b4"> https://github.com/appcelerator/titanium_mobile/commit/a05a7df4e31e...
[INFO] Titanium SDK version: 1.6.0 (02/08/11 20:55 bd9d124...) galaxy tab (2.2.2) G1 (1.6) Nexus S (2.3) sim 2.1