-
-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange behaviour, maybe an error when using peek on Android 5.1.1 #2761
Comments
This is caused by some Android-specific internal lambda expression handling, but it's impossible to debug without full stacktraces. Can you attach those as well? |
I don't think I will be able to, as no error is occurring. I wait for a minute or two, then I stop the app. This is the complete log generated by the emulator. This is not that bad because Android 5.1 pratically dead, but in a corporate enviroment some devices live a long time.
|
The following code runs fine on newer Android versions. However, I've encountered an issue on Android 5.1.1.
After an HTTP request is returned, attempting to use peek to retrieve either the data or an error response results in unexpected behavior.
My request looks like this:
I expect the result to be received in my view model. Here's a simplified example of the expected behavior:
Neither the failure nor the success callback is triggered in the view model. However, I observed the following log message:
If I rewrite this using the following, it works:
The text was updated successfully, but these errors were encountered: