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
Now when the network is down, it takes 25 - 30 seconds for Picasso to render an image. However, if the okHttp3 client is run in standalone mode - outside picasso, the interceptor is called every time and the behavior of the okHttp3 client is consistent and can be rationalized. However, once this client is placed into Picasso, the interceptor is not called - it's as if it is not being used. The imagePath does contain the "scheme" - http in this case, so I am not sure what is wrong with this code or what is being missed but it is very consistent: whenever network integrity is in question, it takes 25 - 30 seconds before Picasso gets the image from cache or disk and renders it.
The text was updated successfully, but these errors were encountered:
Now when the network is down, it takes 25 - 30 seconds for Picasso to render an image. However, if the okHttp3 client is run in standalone mode - outside picasso, the interceptor is called every time and the behavior of the okHttp3 client is consistent and can be rationalized. However, once this client is placed into Picasso, the interceptor is not called - it's as if it is not being used. The imagePath does contain the "scheme" - http in this case, so I am not sure what is wrong with this code or what is being missed but it is very consistent: whenever network integrity is in question, it takes 25 - 30 seconds before Picasso gets the image from cache or disk and renders it.
The text was updated successfully, but these errors were encountered: