Don't commit transactions after onSaveInstanceState()
- On the tablet portrait view, once the contact details are loaded,
a runnable is posted to a handler to properly setup the fragments
(by showing/hiding the ContactDetailFragment or ViewPager/Tab carousel)
- Since it's posted to a handler, we need to make sure that
onSaveInstanceState has not already been called or at least allow
the fragment transaction to be lost if it has been
- Prevent the runnable from doing anything if the activity is already
destroyed
Bug: 5011890
Change-Id: Ib43278f21eee390202ffe4b7ed4057482c34e61c
2 files changed