title: Fragment - getArguments() returns an empty bundle
body: <p>Hope somebody can help me to understand this:</p>
  
  <ol>
  <li><p>I am using a single-activity app and lots of Fragments that are replaced in the same container, and I am testing my app in a real device with the "Don't keep activities" option enabled</p></li>
  <li><p>When a new fragment is added (using <code><a href="https://developer.android.com/reference/android/app/FragmentTransaction.html#replace(int,%20android.app.Fragment,%20java.lang.String)" rel="noreferrer">FragmentTransaction replace()</a></code> method), I am using the <code><a href="https://developer.android.com/reference/android/app/Fragment.html#setArguments(android.os.Bundle)" rel="noreferrer">setArguments()</a></code> method to pass information to the new Fragment. It works as expected and I can get that information with <code><a href="https://developer.android.com/reference/android/app/Fragment.html#getArguments()" rel="noreferrer">getArguments()</a></code> inside that Fragment. Everything ok so far ...</p></li>
  <li><p>After this, I send my app to background. I see that all the fragments in the stack are being destroyed, again as expected</p></li>
  <li><p>I bring my app to foreground and in the <code>getArguments()</code> method I am getting an empty <code>Bundle</code> (not null, just an empty Object) instead of the one with the data I used in #2</p></li>
  </ol>
  
  <p>According to Android documentation, the arguments supplied in <code>setArguments()</code> will be retained across fragment destroy and creation ... So, my questions are:</p>
  
  <ol>
  <li><p>Does the "will be retained across fragment destroy and creation"  includes the scenario I described?</p></li>
  <li><p>Does the "Don't keep activities" option can mess up with <code>getArguments()</code>/<code>setArguments()</code> if it is enabled?</p></li>
  <li><p>Is there a way to test proper fragment creation/destroy besides the "Don't keep activities" option?</p></li>
  <li><p>What is the better approach to properly keep fragment's arguments "alive"? I could save them in the <a href="https://developer.android.com/reference/android/app/Fragment.html#onSaveInstanceState(android.os.Bundle)" rel="noreferrer">onSaveInstanceState()</a> method, but would like to know if there are more options besides that.</p></li>
  </ol>