Unexpected token '<' and unityFramework is not defined

[haeunyy96]

I am quite new to unity and I have been stuck here for a few days.

If someone could please help me that would be much appreciated... thank you!!!

[UmerrAhsan]

Did you find the solution?

[haeunyy96]

I have not :(

[debbieyuen]

I had this problem with my student's projects. There were a couple of things that we had to fix on our end - though I'm unsure if these were the things that were causing the problem.

1. Within Unity, make sure to hit "Disable" compression within the Player settings. The other modes apparently have been causing bugs.
2. The builds must be clean builds. It did not work with a zipped build folder from itch.io and the files cannot be renamed. I recommend copying the entire build folder over including the index.html build file and the TemplateData folder.

3. For me, [email protected] worked best. I needed to downgrade to 8.x

[Blondemonk]

Unexpected token '<' usually suggests that your server (or wherever you're loading your build/* files from) has returned a html response rather than the file you're after.

When you load the page in Chrome/Firefox, what does the Network tab show for each of the files you're loading? Do any of them load with the wrong mimetype or response?

In particular, in my UnityContext, my files don't have .unityweb at the end of them. If yours do, that's fine; however, if they don't then your server might not be able to find the right file. Even if your server is finding the files, it might not know what type they are (e.g. does it know that a .js.unityweb file should be served as application/javascript, and not something else).

[eastedgeZack]

Looks like it's trying to load the loader.js file as html but I'm not sure why

[eastedgeZack]

What unity version is this? I'm getting it on Unity 2021 and also 2022.3.5f1

[eastedgeZack]

Ah all I had to do was move the build folder to my public folder.

[rutvikER1999]

This works for me

[Igardemi]

It seems it was a permissions or cors problem, solved.
I believe that this problem is due to the cors permissions of the path, the resources are not found in those paths.