Databases
StackOverflow2013
Postsdbo
POorientation change, FragmentTransaction, Activity has been destroyed, WeakReference
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POorientation change, FragmentTransaction, Activity has been destroyed, WeakReference
    primarykey
    data
    text
    <p>Alright. My first question here. And I already found some solution, but honestly do not really get the stuff that happens in the background. So perhaps there’s someone who could clear up this stuff a little bit. After days of debugging I’m just glad that it works... and hope I did not make some serious error. So let’s have a look.</p> <p>I got some Main-Activity. Just a FragmentActivity extending <a href="https://github.com/jfeinstein10/SlidingMenu" rel="nofollow noreferrer">JFeinstein’s</a> SlidingFragmentActivity. Further I decided to go the fragment-way and just put any content (list-fragment, article-fragment, …) as a fragment into a container (to right of the sliding-menu); my main-container. So far, so good.</p> <p>One essential fragment is my article-fragment. A ViewPager (with a FragmentStatePagerAdapter) - containing some pages with text and perhaps another list-fragment. Still no problem so far, until I decide to rotate the device. And to be more precise, rotating the device works too as long as I do not decide to update my article-fragment.</p> <p>I understood (correct me if I am wrong) that Android handles the fragments state on its own when rotating the device. And it seems to be everything fine just until I want to reload/update its content.</p> <p>Ok let’s dig deeper into that. On first start I got some empty main-container. Then I am loading my article-fragment for the first time. Just getting the SupportFragmentAdapter, creating my ArticleFragment and replace the main-container with the newly created fragment - tagged. No rocket-science - just a simple transaction:</p> <pre><code>ViewPagerFragment pagerFragment = (ViewPagerFragment) getSupportFragmentManager().findFragmentByTag(TAG_FRAGMENT_ARTICLE); if(pagerFragment != null){ if(pagerFragment.isResumed()){ pagerFragment.triggerReload(); } } else { pagerFragment = new ViewPagerFragment(); FragmentTransaction t = getSupportFragmentManager().beginTransaction(); t.replace(R.id.id_main_root_frame, pagerFragment, TAG_FRAGMENT_ARTICLE); t.commitAllowingStateLoss(); } </code></pre> <p>To avoid creating a fragment each time I reload my content, I’m trying to fetch the fragment before the transaction and - if it is found and resumed - trigger some reload on the existing fragment.</p> <p>Now I rotate my device in this state. To avoid messing with the fragment state I left onSaveInstanceState() inside the fragment untouched. So I guess the fragment is just destroyed and recreated. And everything still works so far. But I think this part has something of a black box.</p> <p>After that - normal startup, creating fragment and put into main-container, rotating device - I trigger some update. But instead of finding the old (recreated) fragment by tag, nothings found and a new fragment is created and inserted. At least tried to be inserted, because this is where I got the following exception:</p> <pre><code>java.lang.IllegalStateException: Activity has been destroyed </code></pre> <p>To be precise, I get the above exception when finish my transaction with a commitAllowingStateLoss(). When I just commit() the transaction I get the following exception:</p> <pre><code>java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState </code></pre> <p>So that’s where the error comes up. And after ages of debugging and searching I found some hint on <a href="https://stackoverflow.com/a/14222708/1378311">this question/answer</a> to get the SupportFragmentManager on a WeakReference of my MainActivity. And what should I say. Since I implemented that, it works. I had to change my update-process a bit, but it works. But leaves some questions ...</p> <p>The behaviour seems to be similiar. First creation works perfect. Reload just the same - fragment is found by tag. After rotation, article is still shown. And when I reload the fragment with that state it is not found by tag so a new one is created, but the commit()-request does not throw an exception. A look inside the debugger shows that the WeakReference is some other instance (other id), than the one(this) all of this takes place in. And thats where I lose the plot. ..</p> <p>If some of you could give me some hints, would be great! Thanks in advance!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USmauricemoss
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POorientation change, FragmentTransaction, Activity has been destroyed, WeakReference
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POorientation change, FragmentTransaction, Activity has been destroyed, WeakReference
      1. USPhpXp
      1. VTFavorite
    3. VO
      singulars
      1. POorientation change, FragmentTransaction, Activity has been destroyed, WeakReference
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have the exact same issue and not the slightest clue why it is behaving this way. Super frustrating since none of this stuff is documented.
      singulars
      1. POorientation change, FragmentTransaction, Activity has been destroyed, WeakReference
      1. USdcow
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload