Strange behavior when Activity calls destroy

[shawel]

Hi,

Great framework, thanks for providing it. I found a bug that I could not solve though. I have a menu item that starts a child activity on top of the tab activity using your framework. For some reason while dismissing the child activity the tabs are no longer visible, the area is empty. Now this does not happen on all phones. It works great on some phones, but my testing on my samsung galaxy s3 for some reason calls destroy on the parent activity and it the result is what I described above. What I found out was since after destroy onCreate had to be called createTab never gets called because saveinstance bundle is not null. but removing that piece of code give me a strange result where the fragments attached to the last selected tab gets painted on all the tabs (or the tab is officially not working at that point anyway) i.e detached for any of the fragments.