[AC-2986] ActivityIndicator crashes after returning from external web browser on android.
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2011-07-09T12:13:54.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Appcelerator Modules, Titanium SDK & CLI |
| Labels | android, crash, defect, release-1.7.0 |
| Reporter | Julian Lindblad |
| Assignee | Tony Guntharp |
| Created | 2011-07-04T01:14:59.000+0000 |
| Updated | 2016-03-08T07:47:59.000+0000 |
Description
When using a ActivityIndicator in an application and a openUrl-function to open an external web browser, when pressing the back button in the browser, any ActivityIndicator in the program will produce an exception and eventually crash the program.
The following error message is shown: [http://pastie.org/2161668]
The following code will reproduce the bug: [http://pastie.org/2161675]
Make sure to wait for the page to finish loading så that the app is relaunched and not just returned to (which is another issue of mine).
A question and answer post here: [http://developer.appcelerator.com/question/121996/]
Okey, so I found some more clues. Apparently I get low memory on my android device (emulator) which forces my application to close. Is there a way to increase it's memory to prevent it from crashing? Complete console output: [http://pastie.org/2161859] Although the memory seems to be the root to my problem, the problem with ActivityIndicator crashing after a program crash still exists.
Julian It's great that you created [a Q&A question](http://developer.appcelerator.com/question/121996/activityindicator-crashes-after-returning-from-external-web-browser-on-android) to consult the community before raising this ticket, as this is the recommended approach. However, it's useful to also include a link to it in the ticket for reference. I think the problem may be caused by the way you are using the API. See my answer in the Q&A. If it transpires that this really is a bug, I will be happy to reopen this ticket. Thanks
Posted a modified version of my code as a comment to your answer. Never the less, even if it turns out that this is a problem caused by my misuse of the API, shouldn't it at least be fixed so it does not crash. Or at least specified in the documentation.