@yaustar @mvaligursky
Hello together, hope youre doing fine!
I’m encountering a TypeError: Cannot read properties of undefined (reading 'failed') related to shader handling in PlayCanvas v1.77.0 Here’s the relevant snippet that fails:
var p = c.getShaderInstance(a, 0, s, o, this.viewUniformFormat, this.viewBindGroupFormat)
, m = p.shader;
if (!m.failed) { { ... } // Error: Cannot read 'failed' of undefined
Screenshot:
That resolves the runtime crash, but I’m wondering if this is a regression or expected in v1.77.0
Note: the project is live a while and we hadnt experienced those errors since then - last week we had a test run for an update and everything worked too. nothing changed in our code to load assets from storage and adjusting the corresponding materials, so now im wondering if there maybe was an update or something in this case in the last (3-4) days?
Best regards
I was just about to post about this. I am having the same problems and it now halts me from releasing new versions of my game. I’m happy I am not the only one.
I don’t experience the problems in editor, nor in quick published (“Publish in PlayCanvas”). I only experience the problem in builds I get through downloading a .zip file and publishing that.
1 Like
I’m no longer at PlayCanvas so I can’t help with support
1 Like
It seems we have an issue where if the project using V1 engine (lets say 1.77.0) is published using the REST API, and the engine version is not specified in that call, an incorrect engine is used.
I’d be curious to see if that’s your issue. If so, the temporary fix is to specify 1.77.0 to the rest call, till we fix the default value.
2 Likes
@yaustar
Oh, that’s really unfortunate—I really appreciate your support over the past few years! I wish you all the best! 
@mvaligursky
Yes, I really think this could be the main issue, because running the project within the PlayCanvas Editor or hosted via PlayCanvas worked as expected. But as soon as we published the project/builds onto the server, we encountered those issues since a few days.
That’s why I thought something in the build pipeline of PlayCanvas must have changed in the last few days. Some shaders (also the tween.js library) aren’t compatible with v2, I guess, and it seems our project wasn’t built with the v1 (even though we built with version 1.77.0) pipeline but with v2.
I had to create a workaround for those sections yesterday (pressure on 
) because we had an important update that had to go online—i would say the build issue was really bad timing! 
