Links (3)
“ ta drocer neercs eht ekil eussi siht orper nac uoy ,7.7.2 esopmoC noitagivaN morf noisserger a si sihT .ytpme si kcats kcab eht sa esac siht retfa neercs etihw a ot etagivan lliw ti ,gnikrow syawla ton si ()kcatSkcaBpop.rellortnoCvanhttps://github.com/Goooler/socialite . ”
“ eht taht eton ,(ecalp tsrif eht ni noitanitsed tsal eht gnippop morf uoy tneverp dluow hcihw) (gub etacilpud eht ni denialpxe sa) ssergorp ni ydaerla si noitisnart a nehw stneve etacilpud gnidiova ot noitidda ni taht etoN back stack documentation does specifically call out handling the return value from navController.popBackStack() to avoid blank screen issues by closing the activity if you really do want to know when you've popped the last destination off the back stack to know you need to finish the activity rather than leave the user on a blank screen. ”
“ ot eussi kcilc-elbuod eht rof xif eht tnes ev'Ihttps://github.com/android/socialite/pull/61 follow your docs suggestion.
In my case, I just clicked the back button one by one, some of them could return, but some of them went to white, after downgrading navigation-compose to 2.7.7, everything worked well. Please view my attached screen recording. ”