-
Notifications
You must be signed in to change notification settings - Fork 9
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
Getting "null is not an object" sometimes #18
Comments
Hi, This will be hard for me to fix if it's not possible to reproduce unfortunately. Maybe it is affecting only a subset of your users and you have more context about the user environment (I mean, maybe it's only a specific version of a specific browser) Sharing the full stacktrace, not just the error message, might be helpful as well. |
Yeah, I might imagine, sorry for that, I'd happily submit more if I only have it 🙂 |
Maybe someone else will come up with more infos someday 😅 Could as well be a bug in https://github.com/bjoerge/debounce-promise, the underlying lib Also sometimes bugs like that are triggered for weird reasons like browser plugins that affect the dom in a weird way. |
I have the same problem in a react native app: It is reported on production every now and then but I was not able to reproduce it. Just to let you know. |
thanks what's your RN version and runtime? JSC (default), V8, Hermes? have you reported it to the original repo? as the error is thrown here? |
No, sorry I implemented the functionality with lodash's debounce function now. |
React native is 0.63.3 with hermes js. Until now I just had the report on android devices, but our iOS release may have the same issue (iOS version is released since a few days only) |
Thanks. Let me know if you have the problem on iOS as well, but it's likely to also be on iOS if @NOtherDev see it on Safari and Chrome. |
@bjoerge any idea? Has someone else reported the problem? |
Unable to reproduce myself, but Bugsnag reports this error several times a day on production, in
node_modules/debounce-promise/dist/index.js:54:141
:I believe it's some kind of race condition when the
deferred
object was already cleared.We use ADP in React component like this:
The text was updated successfully, but these errors were encountered: