-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Please report: Excessive number of pending callbacks: 501 #2171
Comments
have same problem |
getting same warning on RN 70 |
getting same warning 70.5. |
Just wanted to let you know what worked for me, I replaced onDayPress with onDayChange |
I looked at this as a solution as well however, onDayChange does not fire when a day press event is fired. So, if you use onDayChange there is no way to fire off an action when you press a day (especially if you are using showOnlySelectedDayItems) |
There is a bug with TouchableOpacity rn 70.5. Can update to rn 71 to get rid of this warning or try to use below patch. |
Wanted to mention that I upgraded to rn 71 and the issue is still present. |
The same is happening to my code. The bug appeared after I updated my expo SDK from 45 to 48. |
Update the version of React Native with:
And I changed the onDayPress method to onDayChange and it worked for me. |
I'm still facing this too. The |
Me too. RN69.9 When
Is facebook/react-native#34442 helpful? |
@jorgeestebancl12 Why was this closed? this is still an issue in the latest version with the
|
I am also still getting this issue, what's the ultimate solution? |
Hello, I hope you are very well, I am receiving a warning in a specific case.
I am creating an agenda that consumes the data from a useEffect and some useState variables which are:
When I do this at first it works correctly, but when I want to add the theme property and assign values to it, it starts giving the warning, if I remove the theme property it continues to work fine, any idea what it could be? thank you.
the theme property I'm sending is just this:
I also attached the full warning:
If anyone has an idea of how to solve it, I would appreciate it, thank you very much.
The text was updated successfully, but these errors were encountered: