Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, you should read my <a href="http://www.androiddesignpatterns.com/2013/08/fragment-transaction-commit-state-loss.html" rel="noreferrer"><strong>blog post</strong></a> for more information (it talks about why this exception happens and what you can do to prevent it).</p> <p>Calling <code>commitAllowingStateLoss()</code> is more of a hack than a fix. State loss is bad and should be avoided at all costs. At the time that <code>onActivityResult()</code> is called, the activity/fragment's state may not yet have been restored, and therefore any transactions that happen during this time will be lost as a result. This is a very important bug which must be addressed! (Note that the bug only happens when your <code>Activity</code> is coming back after having been killed by the system... which, depending on how much memory the device has, can sometimes be rare... so this sort of bug is not something that is very easy to catch while testing).</p> <p>Try moving your transactions into <code>onPostResume()</code> instead (note that <code>onPostResume()</code> is always called after <code>onResume()</code> and <code>onResume()</code> is always called after <code>onActivityResult()</code>):</p> <pre><code>private boolean mReturningWithResult = false; @Override protected void onActivityResult(int requestCode, int resultCode, Intent data) { super.onActivityResult(requestCode, resultCode, data); mReturningWithResult = true; } @Override protected void onPostResume() { super.onPostResume(); if (mReturningWithResult) { // Commit your transactions here. } // Reset the boolean flag back to false for next time. mReturningWithResult = false; } </code></pre> <p>This might seem a little weird, but doing this sort of thing is necessary to ensure that your <code>FragmentTransaction</code>s are always committed <em>after</em> the <code>Activity</code>'s state has been restored to its original state (<code>onPostResume()</code> is guaranteed to be called after the <code>Activity</code>'s state has been restored).</p>
    singulars
    1. This table or related slice is empty.
    1. PO"Failure Delivering Result " - onActivityForResult
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt
    1. USAlex Lockwood
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO"Failure Delivering Result " - onActivityForResult
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIn Fragments, I'm using onResume in the absence of onPostResume. I haven't seen the issue again, but perhaps you want to comment on this. PS. Thanks a lot for your insightful posts!
      singulars
      1. PO
      1. USMaragues
    2. COYes, doing this in `Fragment#onResume()` is fine. This is because `FragmentActivity#onPostResume()` calls `FragmentActivity#onResumeFragments()`, which calls `FragmentManager#dispatchResume()`, which calls `Fragment#onResume()` for each of the activity's fragments. Therefore, `Fragment#onResume()` is called after `FragmentActivity#onPostResume()` so there won't be a problem (you can check out the [source code](http://goo.gl/Lo1Z1T ) for each respective class to verify this for yourself... or you can just just me :P). And thanks! Glad you thought they were insightful. :)
      singulars
      1. PO
      1. USAlex Lockwood
    3. CO@Alex, If the dialogfragment makes a network call, and the Home button is pressed before the dialogfragment gets the async response, invoking this.dismiss() within the async response will cause a state loss exception. In this scenario, when should dismiss() be invoked so that there is no state loss? Note that request and response are within the dialogfragment, not within the activity.
      singulars
      1. PO
      1. UScrazy horse
 

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