-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
undefined is not an object (evaluating 'this._data[this._data.length-1].push') #329
Comments
Just seen again on another instance of the app:
|
I also can see that Issue on Chrome Mobile v.56.0.2924/64.0.3282 on Android v.7.0 |
I'm joining the club with the error messages: Our tracking said it's a Samsung SM-T5851 with Chrome 64.0.01 and running Android 7.0.01 Minified stack trace:
|
+1 |
1 similar comment
+1 |
Same issue: Also this straight after the error above: And the issue has been open since January and got no answers =/ |
Maybe the TypeScript rewrite (-> version 3) from @szimek will remove this error. We also have got a report about it via Sentry for Mobile Safari 12.0 on iPad with iOS 12.1.1. We are currently using Signature Pad version 2.3.2. |
I think I've found the solution: Add the following line inside the o.prototype.clear function (above everything else): |
@busiweb did it work? If so, do a pull request with the fix, plz |
Saw this reported on a Safari 12.1 / iOS 12.2 device :( |
Also experiencing this issue. iPad with iOS 12.2 |
Also experiencing this issue, Samsung SM-J730G with Android 7.0. Any update on this? |
Also experiencing this issue on iPhone 11 Pro with iOS 13.4.1. It doesn't seem to cause a problem for the end-user but now that my App has error logging it is rather annoying receiving alerts about this. |
@UziTech As far as I'm aware, this issue hasn't been resolved. I'm assuming it's been closed to clean up issues that are stale? |
If this is still an issue you can open another issue with more information. As far as I know this issue has been resolved in the latest beta release. |
Ah, my bad. I looked at the tags and didn't see a beta 4 tag. I didn't realize that beta 4 had only been pushed to NPM. |
can someone confirm that the issue is fixed? the changelog https://github.com/szimek/signature_pad/blob/master/CHANGELOG.md#300-beta4 only references another issue #480 instead of this one. |
Looking at #481, I believe it should have fixed this as well. The early return for the race condition there is in the same method as this issue. So, if I understand correctly, if That is of course only if the root cause for this error is the same race condition (that causes this to evaluate to a buggy |
Hey,
I'm just raising this for your visibility / in case you have any ideas. I don't have a repro and am not expecting you to be able to do anything to solve this.
We're getting this error thrown on one of our production apps. We have lots of apps running out there and only one has ever had this issue, which suggests to me it might be device related.
The error
Is being thrown from here:
https://github.com/szimek/signature_pad/blob/master/src/signature_pad.js#L173-L178
That's pretty much all the info I have. The client using the app hasn't reported anything to us from a behaviour perspective.
Other info:
I am tracking the issue and will update you if I get further information.
Thanks for all your hard work on this repo,
Stephen
The text was updated successfully, but these errors were encountered: