search

bluelinelabs / Conductor

A small, yet full-featured framework that allows building View-based Android applications
Apache License 2.0
3.9k stars 343 forks source link

When pushing new controller when app is in background, view is not rendered upon returning #618

Closed ursusursus closed 4 years ago

ursusursus commented 4 years ago

Hi, I run some async action, press home button, activity is in background, now the async action finished, it causes a pushController.

I observe correct callbacks on the new controller, it gets created, onCreateView, onAttach-ed; however if I return the activity to foreground, the screen is empty

Is this indended behaviour? I thought conductor allowed for pushing of new controller after onSavedInstanceState unlike fragments

ursusursus commented 4 years ago

if I don't use change handlers, just the plain RouterTransaction.with(controller) it works as should.

My suspicion is that the change animator just simply dont get played

ursusursus commented 4 years ago

Ok its a problem in my custom change handler implementation, some values on view are 0 then and it animates from 0 to 0 basically

Sorry, I got scared there a little as this was my main buyin point to Conductor