paging library: how does the library figures out if it needs to reload data on configuration change?...

# android

[solidogen]

paging library:
how does the library figures out if it needs to reload data on configuration change? it always shows old data for a split second, then immediately scrolls to top and does refresh+append. I’m not sure what can cause this, samples do not have this behavior - load method is not even called

I can’t even debug it, debugger points me to .class files, breakpoints in kotlin equivalents don’t hit

[Robert Munro]

suspend function dont work too well with the debugger - might have to just log data

[solidogen]

I can’t log data inside library without forking it, but I managed to get breakpoints working

[solidogen]

okay, my Pager was a getter instead of the field 🤦