We started getting this about a month ago after an OTA update on our Expo 38 version, and it kept happening even after we updated to Expo 42 (sentry-expo 4.0.1, @sentry/react-native 2.6.0). It’s an error with no source map, not Expo tags, no Sentry SDK version, and no OS/ system info.
I’ve made an example of the error public here: Sentry
They all look about the same: between 1 and several hundred events with zero user account. Non-fatal “Type error: u is not a function” with a big long file path in the breadcrumb, like this:
That breadcrumb contains a device-specific GUID, so, of course, EVERY SINGLE ONE of these errors shows up separately in in Sentry, absolutely flooding my list.
I have not heard any user reports of adverse things happening that I could trace back to this error. Non-fatal JS error on what looks like very early-running code has me concerned that maybe the expo-update process is crapping out, leaving the user stuck at the splash screen (had a couple of iOS review rejections in recent months because the reviewer said they got stuck at the splash screen).
Sentry support hasn’t been much help. I’d love to hear if this has happened to anyone else, or if anyone has any clue as to what might be happening, or if you know the magic words to get Sentry to not be like “uh, that’s sentry-expo, we don’t touch that.”