Skip to main content
S
Sal-la
New Participant
December 7, 2017
Answered

Error "handle value is not a number"?

  • December 7, 2017
  • 3 replies
  • 6171 views

Hi! I'm getting this error all the time now when ever I try to do some changes to my scene and I have no idea what it is all about: "handle value is not a number. Error code: (Container.js:215)" and it's making me mad...!

      This topic has been closed for replies.
      Correct answer Jeff Almasol

      Hello all... The updated version of Character Animator, version 24.2, is now available in the Creative Cloud desktop app. It contains the fix (previously only available in the Beta build) for this issue. Thank you for your patience and help resolving it.

      3 replies

      Jeff Almasol
      Adobe Employee
      Jeff AlmasolCorrect answer
      Adobe Employee
      February 8, 2024

      Hello all... The updated version of Character Animator, version 24.2, is now available in the Creative Cloud desktop app. It contains the fix (previously only available in the Beta build) for this issue. Thank you for your patience and help resolving it.

      W
      wael5CE7
      New Participant
      February 14, 2024

      I have 24.2 and it's giving me this error constantly.  What should I do?

      Jeff Almasol
      Adobe Employee
      Jeff Almasol
      Adobe Employee
      February 15, 2024

      Hmm, sorry that 24.2 isn't completely solving the issue for you. Are you seeing this when you are opening a scene that contains a puppet that uses Dangle?

      Are you seeing it if you start a new project and use the Chloe template puppet (from the Home screen)?

      We might need to get a copy of the project that contains the scene/puppet causing the issue to diagnose further. If you'd like us to diagnose a specific project, can you archive the project folder as a .zip file, then send me a direct message with a shared link to the .zip file?

      Thanks.

      K
      kind_rebel98A2
      New Participant
      September 14, 2019

      After getting this annoying message, I searched and what I saw here, gave me a clue and I went back and deleted the dangles and added them back and it was fixed. So I suppose there is an issue with the dangle handles.

      alank99101739
      alank99101739
      Brainiac
      September 14, 2019
      I think there was a previous problem for dangles not over artwork or in the right mesh. You might have fixed it without realizing when creating again
      DanTull
      Adobe Employee
      DanTull
      Adobe Employee
      December 12, 2017

      I'd be curious to see this project. I have seen an error like this in a rather abusive use of the Physics behavior, but I have seen it occur in analytics just often enough that it makes me think there is some more mainstream use that hits it as well.

      If you'd be willing to share a project that is exhibiting the error more commonly, I'd be interested in doing a deeper diagnosis. If you're interested, I can contact you privately with contact information.

      Thanks -- Dan Tull

      alank99101739
      alank99101739
      Brainiac
      December 12, 2017

      I have my project up in Adobe Cloud, and am happy to share it with you. Just reach out to my email and I will work out if I can just share the whole project with you then email you directly instructions on the most likely way to trigger the problems I typically see.

      DanTull
      Adobe Employee
      DanTull
      Adobe Employee
      December 13, 2017

      Thanks for the assist on the Container.js "handle is not a number" error. I haven't personally tried to make it happen just yet, but the video and project give me some excellent leads to follow for what's causing it. I'm hopeful that it'll be enough for me to pin it down.

      Thanks! -- DT

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices