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
First, I apologize that I can't isolate the precise cause of this error, or even duplicate it. It has showed up in our Sentry reports since we updated to the latest version of InstantClick from the initial 3.1 release.
We've seen the following error report twice so far, and both times it happened in Chrome Mobile on Android devices.
The exceptions come in pairs: TypeError: Cannot convert undefined or null to object is reported at line 360. Then Cannot set property '116' of undefined (or some other integer in the quotes) at line 379. I interpret these errors as meaning that $timers[$currentLocationWithoutHash] is undefined. For one reason or another, we are not getting a stacktrace beyond these points.
Does this ring a bell? Again, I'm sorry I can't provide more information. If I find out more, I'll let you know.
The text was updated successfully, but these errors were encountered:
We are continuing to see this error in our reporting. There were 85 instances of it reported yesterday. All of the errors have occurred on devices running various versions of Android. Most reported Chrome Mobile as the browser, but Android's browser and "Facebook" also show up.
First, I apologize that I can't isolate the precise cause of this error, or even duplicate it. It has showed up in our Sentry reports since we updated to the latest version of InstantClick from the initial 3.1 release.
We've seen the following error report twice so far, and both times it happened in Chrome Mobile on Android devices.
The exceptions come in pairs:
TypeError: Cannot convert undefined or null to object
is reported at line 360. ThenCannot set property '116' of undefined
(or some other integer in the quotes) at line 379. I interpret these errors as meaning that$timers[$currentLocationWithoutHash]
is undefined. For one reason or another, we are not getting a stacktrace beyond these points.Does this ring a bell? Again, I'm sorry I can't provide more information. If I find out more, I'll let you know.
The text was updated successfully, but these errors were encountered: