<p>I'm using the current Google Analytics tracking code, and on Firefox 59 I get this error in console: </p> <blockquote> <p>unreachable code after return statement</p> </blockquote> <p>On this javascript: https://www.googletagmanager.com/gtag/js?id=UA-my-tracking-code:formatted</p> <p>Since this problem doesn't seem to be googleable, hence it seems others do not have this problem, my guess is that it's me who does something wrong. But what this could be?</p> <p>I'm putting the snippet in <code><head></code>, just like the docs say:</p> <pre class="prettyprint"><code><!DOCTYPE html> <html> <head> <title>some title</title> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0">  <script async src="https://www.googletagmanager.com/gtag/js?id=UA-my-tracking-code"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-my-tracking-code'); </script> </head> <body> blah blah </body> </html> </code></pre>

<p>It is <em>not</em> your fault. If you prettify the code with Firefox's it can be found here:</p> <pre class="prettyprint"><code>Gc = function (a, b, c) { var d = a.split('.'); var e = function (a, b) { for (var c = 0; void 0 !== a && c < d.length; c++) { if (null === a) return !1; a = a[d[c]] } return void 0 !== a || 1 < c ? a : b.length ? e(Hc(b.pop()), b) : Ic(d) }; return e(Cc.eventModel, [ // <= True return value b, c ]); return Ic(d) // <= This can never be reached! }, </code></pre> <p>To prettify the code:</p> <ol> <li>Click on the warning's blue link. You'll see the garbled code.</li> <li>Click on the icon with the <code>{}</code> on the bottom left of that panel to prettify it. However the reference will be lost.</li> <li>Go back to the "Console" panel and click again in the same warning's blue link. Now you'll see the original reference in the correct line.</li> </ol> <p>Firefox is correctly pointing the bug, the function <code>Ic(d)</code> will never be reached since the function returns earlier. Seems like a Google Tag Manager bug, however without inspecting the original code we cannot tell the severity.</p>

<p>My OCD will not let this be. Warnings are as bad as errors to my brain... lol</p> <p>The answer provided by @Me - caused me to perform the following:</p> <ol> <li>Navigate to the url in the <code><script async src="https://www.googletagmanager.com/gtag/js?id={Google Analytics Id here}"></script></code> tag and grab a copy of the JavaScript.</li> <li>Drop it into a file in my solution and replace the remote js src with this new local copy.</li> <li>Re-format the file (prettify).</li> <li>Comment out the offending line (if it can't be reached as-is I don't expect terrible harm to come from simply removing it).</li> </ol> <p>The warning is gone, and so far everything seems to be working - no additional or new errors/warnings in the console and Analytics/Tracking data still seems to be coming through. </p> <p>This is clearly not an ideal solution - I'll have to continue monitoring this until either a) Google fixes their code (which, incidentally, omits semi-colons all over - I doubt it'd come close to passing a Linter) or b) Google makes other changes to the code, causing mine to break or my Analytics to stop reporting.</p>

"unreachable code after return statement" error in Google Analytics JS code on Firefox - is this my fault?

Tags:

I'm using the current Google Analytics tracking code, and on Firefox 59 I get this error in console:

unreachable code after return statement

On this javascript: https://www.googletagmanager.com/gtag/js?id=UA-my-tracking-code:formatted

Since this problem doesn't seem to be googleable, hence it seems others do not have this problem, my guess is that it's me who does something wrong. But what this could be?

I'm putting the snippet in <head>, just like the docs say:

<!DOCTYPE html> <html>     <head>         <title>some title</title>         <meta charset="UTF-8">         <meta name="viewport" content="width=device-width, initial-scale=1.0">          <!-- Global site tag (gtag.js) - Google Analytics -->         <script async src="https://www.googletagmanager.com/gtag/js?id=UA-my-tracking-code"></script>          <script>           window.dataLayer = window.dataLayer || [];           function gtag(){dataLayer.push(arguments);}           gtag('js', new Date());           gtag('config', 'UA-my-tracking-code');         </script>      </head>     <body>      blah blah      </body> </html>

946

asked Apr 28 '18 19:04

konrados

Video Answer

2 Answers

It is not your fault. If you prettify the code with Firefox's it can be found here:

Gc = function (a, b, c) {   var d = a.split('.');   var e = function (a, b) {     for (var c = 0; void 0 !== a && c < d.length; c++) {       if (null === a) return !1;       a = a[d[c]]     }     return void 0 !== a || 1 < c ? a : b.length ? e(Hc(b.pop()), b)  : Ic(d)   };   return e(Cc.eventModel, [         // <= True return value     b,     c   ]);   return Ic(d)  // <= This can never be reached! },

To prettify the code:

Click on the warning's blue link. You'll see the garbled code.
Click on the icon with the {} on the bottom left of that panel to prettify it. However the reference will be lost.
Go back to the "Console" panel and click again in the same warning's blue link. Now you'll see the original reference in the correct line.

Firefox is correctly pointing the bug, the function Ic(d) will never be reached since the function returns earlier. Seems like a Google Tag Manager bug, however without inspecting the original code we cannot tell the severity.

143

answered Oct 13 '22 00:10

Me -

My OCD will not let this be. Warnings are as bad as errors to my brain... lol

The answer provided by @Me - caused me to perform the following:

Navigate to the url in the <script async src="https://www.googletagmanager.com/gtag/js?id={Google Analytics Id here}"></script> tag and grab a copy of the JavaScript.
Drop it into a file in my solution and replace the remote js src with this new local copy.
Re-format the file (prettify).
Comment out the offending line (if it can't be reached as-is I don't expect terrible harm to come from simply removing it).

The warning is gone, and so far everything seems to be working - no additional or new errors/warnings in the console and Analytics/Tracking data still seems to be coming through.

This is clearly not an ideal solution - I'll have to continue monitoring this until either a) Google fixes their code (which, incidentally, omits semi-colons all over - I doubt it'd come close to passing a Linter) or b) Google makes other changes to the code, causing mine to break or my Analytics to stop reporting.

answered Oct 13 '22 00:10

challamzinniagroup

Related questions
                            
                                Kubernetes config map symlinks (..data/) : is there a way to avoid them?
                            
                                Koin vs Kodein - Dependency Injection what you prefer? Kotlin [closed]
                            
                                Azure Pipelines: Passing a variable as a parameter to a template
                            
                                How do I make matplotlib work in AWS EMR Jupyter notebook?
                            
                                How to resolve .NET Core package version conflicts
                            
                                SwiftUI and MVVM - Communication between model and view model
                            
                                Coroutines and Retrofit, best way to handle Errors
                            
                                Difference between codeActionsOnSave and formatOnSave in VS Code
                            
                                "Building for iOS, but the embedded framework 'xxx.framework' was built for iOS + iOS Simulator"
                            
                                SwiftUI DatePicker jumps between short and medium date formats when changing the date
                            
                                Basic unit test and C, how do I get started?
                            
                                How to redirect from HTTPS to HTTP without annoying error messages

Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!

Donate Us With