ReferenceError: Can't find variable: gmo

[sentry-io]

Sentry Issue: BESTCODES-DOT-DEV-19

ReferenceError: Can't find variable: gmo
  at global code (app:///:1:4)

This issue was automatically created by Sentry via Sentry events (All)

[The-Best-Codes]

Non GMO?

[Dwizzle252]

Hi @The-Best-Codes,

Would you be able share any details on this error you received? I am looking at a similar error occurring on a site that just started showing this same error and was wondering if sentry collected any additional details for you? I just happened to stumble upon this by searching this error message in GitHub, only you and one other site I've found have this reported. Any info or help is appreciated. Thanks!

[smhg]

@Dwizzle252 I'm getting reports of the same error (non-Sentry).
In my case the useragent hints it might be only happening inside the Google Search App on iOS.

EDIT: it seems to be related to version 354 of that app in my case. I didn't get any reports for version 355 (the current version), yet.

[Dwizzle252]

Thanks @smhg. I'm seeing the same GSA 354 in the in the user agent. Just missed this previously. I also see some listed as 355, so this may still be an ongoing bug with them. Going to try to replicate more & possibly submit this as an issue with them.

[ketijakrista]

I also found this by google search. All our sites report this error on Sentry, can't find the source :/ Started February 6, is it the same for you? Only iOS, browser Google, seems that real users, not bots. No other information.

[Dwizzle252]

@ketijakrista We had noticed the same thing - real users and 2/6 start date that you described. I was actually able to replicate the error on the google search app on ios running app version 355. I reported it from inside the app as a issue. Not sure if that was the right place to submit it for visibility. I know Google has a bug board, might try there next.

[ketijakrista]

Found this, I guess yours, will give it a plus https://issuetracker.google.com/issues/396043331

Edit: Thank you all!

[LinziBligh]

We are also getting this same error pinging us from both Sentry and Datadog, first noticed on 2nd January, but ramping up in number dramatically in last week or so. Thanks for flagging!

[ramchandra-st]

We also noticed similar error since yesterday. Looking forward to see more details on this.

[The-Best-Codes]

@Dwizzle252 and others, are you using Next.js?
I'm using Next.js 15, React 19, and the experimental TurboPack and React Compiler features.
What about you all?

Also, the issue is only iOS with Google for me as well:

[Dwizzle252]

@The-Best-Codes I’m only using react 16, not using next.js. I’d be curious anyone is experiencing the issue on a project that doesn't have a react dependency.

[ketijakrista]

@The-Best-Codes Next 14, React 18 here

[The-Best-Codes]

@Dwizzle252
Very interesting, I think that rules out React compiler and such...

I don't have an iOS device to test this on. I might create a simple site using vanilla JS with sentry and see if someone here can try it in Chrome on iOS.

[The-Best-Codes]

Looks like Honey Badger is also collecting this issue.
LBH3/lbh3.org#496

[edwh]

@Dwizzle252 and others, are you using Next.js?

Nuxt/Vue here, no React.

[The-Best-Codes]

Nuxt/Vue here, no React.

Thanks for sharing. It's looking like a Google bug, as @Dwizzle252 guessed.
Give the issue a plus and hopefully Google with fix it soon:
https://issues.chromium.org/issues/396043331

[The-Best-Codes]

I might create a simple site using vanilla JS with sentry and see if someone here can try it in Chrome on iOS.

No need for this now...

[jasand-pereza]

We're using Next.js and see these errors as well.
Does anyone know how to mute this error in Sentry? It keeps reporting a new error for every affected page URL. Maybe I have to update inbound filters or fingerprinting.

[The-Best-Codes]

@jasand-pereza
https://docs.sentry.io/product/issues/states-triage/#archive

Archiving it worked for me:

But so far I've only had one page affected.

[pjsg]

I see this in the google versions below. My site doesn't use any framework -- just some jquery. Yes, all iOS, several different versions. Started on Jan 4th.

Google 355.0.723646882
52%
Google 354.0.720749604
47%

[ketijakrista]

We added to ignore list in sentry.client.config.js, if anyone wants to save their error reporting limits.

[martin-juul]

@Dwizzle252

We're seeing it on our angular 17 application

[petrosoft-fi]

We're seeing it in our Svelte app with custom error logger. Started few days ago and increasing.

"userAgent": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_6_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) GSA/354.0.720749604 Mobile/15E148 Safari/604.1",
"error": "ReferenceError: Can't find variable: gmo",
"lineno": 1,
"colno": 4,
"stack": "global code@https://censored-domain.com:1:4",

[sb-chericks]

Same issue, same device and browser environments, React 18. Repping the issue tracker on chromium.

[jasand-pereza]

@jasand-pereza https://docs.sentry.io/product/issues/states-triage/#archive

Archiving it worked for me:

But so far I've only had one page affected.

Thanks @The-Best-Codes!

[guglielmi-s]

useragent
Mozilla/5.0 (iPhone; CPU iPhone OS 18_1_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) GSA/355.0.723646882 Mobile/15E148 Safari/604.1
os
iOS 18.1.1 27% iOS 18.3.0 23%

[The-Best-Codes]

getsentry/sentry-javascript#15432 addresses this issue and is released in Sentry 9.2.0.

[The-Best-Codes]

Since my site just uses Sentry, I'm going to close this as completed now.

[Flcwl]

@Dwizzle252 I'm getting reports of the same error (non-Sentry). In my case the useragent hints it might be only happening inside the Google Search App on iOS.

EDIT: it seems to be related to version 354 of that app in my case. I didn't get any reports for version 355 (the current version), yet.编辑：在我看来，这似乎与该应用程序的 354 版本有关。我_还_没有收到 355 版本（当前版本）的任何报告。

no, I get reports for version 355