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
{{ message }}
This repository has been archived by the owner on Mar 23, 2020. It is now read-only.
I have implemented this library for quite a long time and it is a good ripple for ripple animation. Recently, I found the Bug, while running the Application on a particular Device, which in my case is Nokia 5.1 running on Android 8.1.0.
The Bug, When I start the ripple animation if any push notification comes to my device it automatically stops the Ripple animation. I thought it is a bug on all the devices running on Android 8.1.0 or above but it runs perfectly on other devices running 8.1.0 and even the Pixel running on 9.0.0. I believed this has something to do with the memory of the device. I will upload the stack trace of the memory monitor later. But consider this a legit issue. Please try to fix it.
The text was updated successfully, but these errors were encountered:
i-m-aman
changed the title
is:issue is:open Push Notification Stops the ripple Animation. Running on Nokia 5.1 - Android 8.1.0
Push Notification Stops the ripple Animation. Running on Nokia 5.1 - Android 8.1.0
Mar 25, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have implemented this library for quite a long time and it is a good ripple for ripple animation. Recently, I found the Bug, while running the Application on a particular Device, which in my case is Nokia 5.1 running on Android 8.1.0.
The Bug, When I start the ripple animation if any push notification comes to my device it automatically stops the Ripple animation. I thought it is a bug on all the devices running on Android 8.1.0 or above but it runs perfectly on other devices running 8.1.0 and even the Pixel running on 9.0.0. I believed this has something to do with the memory of the device. I will upload the stack trace of the memory monitor later. But consider this a legit issue. Please try to fix it.
The text was updated successfully, but these errors were encountered: