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: