You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The presenter is recreated each time a new instance is created, as during a rotation. This doesn't address one of the main Android issues.
Let's say you got a network request, initiated by the presenter of the activity before rotation, how can the new instance take advantage of the request pending or resolved ?
The text was updated successfully, but these errors were encountered:
You could improve the example to do it like that, saving somewhere (maybe an static component) that the request has already been done, and requesting it when the presenter is recreated. When you start listening the bus, then you can decide if you execute the request or wait for the response of an old request.
The presenter is recreated each time a new instance is created, as during a rotation. This doesn't address one of the main Android issues.
Let's say you got a network request, initiated by the presenter of the activity before rotation, how can the new instance take advantage of the request pending or resolved ?
The text was updated successfully, but these errors were encountered: