Mentioned issues (1)
Previous fragment is still started when next fragment reaches onViewCreated when reordering “ ni reganam etats wen eht fo trap sa dexif saw taht gub a deedni si etats detrats eht fo palrevo detcepxenu eht ,esac ralucitrap siht nI |
Links (3)
“ eht ni detats sA .stnemetats gol ruoy morf eurt mees hcihw ,(ecneirepxe dlo eht gnitteg ,ecneh dna dlrow wen eht fo tuo gnitpo era uoy sa) emas eht yltcaxe etarepo eslaf reganaMetatSweNelbane dna 4.2.1 tnemgarF taht si noitatcepxe ehT new state manager blog post , the enableNewStateManager(false) API will be going away, moving all fragment users into the new state manager world. ”
“ eht ni tuo dellac yllacificeps sa 085456161/b ni reganam etats wen eht fo trap sa dexif saw taht gub a deedni si etats detrats eht fo palrevo detcepxenu eht ,esac ralucitrap siht nI Fragment 1.3.0-alpha08 release notes as something that only affects the new state manager. ”
“ dluohs uoy ,noitagivaN ni ,ecnatsni roF .daetsni gnisu eb dluohs uoy taht gniredro siht no gnidneped ot evitanretla retteb a yllareneg s'erehT listen for navigation events in order to update global state as a single, atomic operation rather than rely on the ordering of one fragment's downward events and one fragment's upward events from being in a particular order. ”