[TIMOB-19760] iOS: Enabled main thread produces unexpected behavior
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2015-10-23T23:56:43.000+0000 |
| Affected Version/s | Release 5.1.0 |
| Fix Version/s | Release 5.1.0 |
| Components | iOS, Tooling |
| Labels | n/a |
| Reporter | Hans Knöchel |
| Assignee | Pedro Enrique |
| Created | 2015-10-22T03:13:50.000+0000 |
| Updated | 2015-12-02T18:46:05.000+0000 |
Description
The main thread is enabled by default in Ti SDK 5.1.0 and later. This just produced quite a lot unexpected behaviors on my projects, here some of them:
* Click events on some views not working
* Picker does not appear any more
Disabling the usage of the main thread manually resolves all issues. Because of that and the related tickets we received so far (where disabling the main thread resolved them), I would overthink if we really should enable the main thread updates in 5.1.
This is a major breaking change and if we continue with this architecture change, then it should be done for Titanium SDK 6.0, not 5.1.
When we make this default we should do a guide and blog post on this with clear illustration like [~ronaldtreur] did: http://www.slideshare.net/ronaldtreur/titanium-making-the-most-of-your-single-thread
see related ticket. enabling it will affect debugger.
I think, that a full working example guide how to call functions with main thread active would be required. There would be several Appcelerator users, who are confused whats happening in their code
Making the Kroll Thread default for now. PR Master: https://github.com/appcelerator/titanium_mobile/pull/7341 PR 5.1.x: https://github.com/appcelerator/titanium_mobile/pull/7342