When interacting with nested fragments instead of using getSupportFragmentManager we must always use getChildFragmentManager instead. Failure to do so causes obscure issues on app suspend / resume (inner fragment unloads on app resume) due to the fact that inner fragments cannot be removed properly as their parent fragment has already been removed. Moreover, it seems that when child fragment manager is used Android is smart enough to remove child fragments automatically when parent fragment is removed.