Uncaught SyntaxError: Unexpected end of input in utag.js

[Jayakrishnaa]

Hi All,

We see "Uncaught SyntaxError: Unexpected end of input" error under utag.js file for one of our Tealium configuration. It’s totally weird and didn't experienced this error before. Every time when we reload the page we see different syntax error on the utag.js. Therefore, it is completely affecting our Tealium profile and data to be captured. I have attached the screenshot for your reference as well. 

It would be good if someone helped us to fix this issue.

Thank you,
Jay.

[corbinspicer]

Hi Jay,

Please reach out to our support team at support@tealium.com with the name of the account/profile and the URL where your Tealium configuration is implementated, and one of our engineers will be assigned your ticket as soon as possible.

Kind Regards,

Corbin Spicer

Solutions Engineer

[Jayakrishnaa]

Ya sure, I will do that. Meantime just want to check if I can get any reply from any of our folks :) and also we are trying from our side as well to fix the same.

[UnknownJ]

Have you tried republishing, @Jayakrishnaa? It looks like there's a problem with the file itself being truncated, when you view the utag file on Tealium's CDN (and refresh if need be) does it conclude after more like 1,300 lines with the PINIT() function (if you have no bundled tags) or the initcatch function (if you have bundled tags)? If you're only getting 450ish lines, you're not getting the full file.

[Jayakrishnaa]

Hello @UnknownJ, 

Yes, now I have given "No" for the bundle tag and it started working without the sysntax error. I have attached the tag which I have given "NO". We have done that for almost 30+ tags and I feel like that the reason many lines where not fully loaded on the utag.js file. So, even now we are wondering how come that the utag.js file will not load it completely when we give "Yes" for the bundle tag option for third party tags. Please suggest if any.

Thank you,
Jay.

[mitchellt]

Hi @Jayakrishnaa - this kind of error happens to me from time to time.  The last time it was because I used a curly brace instead of a parenthesis in a custom javascript extension. It was not caught during the publish, but when I tested on-page, the error appeared.  Check into your last few changes and check for any stray syntax issues like unmatched parens or curly braces, etc.

Good luck, let us know how it turns out!

[Jayakrishnaa]

Hello @mitchellt, @corbinspicer, and @UnknownJ. I think it’s kind of proxy issue from our local machine. It is tracking fine under our client and other machine. stuck here and thinking to move further. 

[Jayakrishnaa]

We have tried accessing the site from our personal system and it is firing fine. We suspect that the issue occurs on because of network/proxy that might be blocking some files to be loaded or some from our organization.

Does it really happen any time before? We hope that it is totally weird situation that causing the site to be tracked on because of this proxy. Please let me know your inputs on this weird issue if you get a time.