1 person found this helpful
Does your error message literally include <useraccount> in the text or did you redact that? It's totally fine if you did, but for me that message (I recreated a similar condition artificially) contains my actual username so if yours actually says <useraccount> it might be a clue as to the nature of the failure.
Thanks for the reply. I redacted it.
I open Ch Animator and the error prompted again. I read every line of the directory and I found the culprit. I overlooked the user account. The user account that Ch Animator error is giving me is not the same as the User account in my Mac. Some characters are missing at the end. Say for example if my user account is "JohnDoeAdminAccount", the error is giving me the directory, "Users/JohnDoeAdminAcco/...". So I figured maybe there is a limit to how many characters a User Account in a Mac should have. Or maybe Ch Animator is programmed that way. Not sure. And that is why ch animator could not locate the bootstrap.js file because it's trying to locate it in a directory that doesn't even exist.
So I created a new Admin Account with less characters or shorter name, Loaded Character Animator, and the Error is gone.
Interesting, thanks for posting back. I had a few theories about how the path could wind up being different on disk so it would be written successfully but then fail to be found when other code went to read it. One hypothesis was that it was some text encoding conversion corner case due to filesystem paths using a different encoding than the code generating the path. I was about to ask if you could tell me your account name because the rest of the path seemed totally normal.
I'll see if I can recreate this condition on my machine to determine if there's a bug on our side that we need to fix.
Further analysis based on a tip from Paul: the key detail here appears to be that Character Animator cannot open a path which contains an element that ends with a period. An odd case to be sure but still a bug. I'll file that internally.