: Cannot read property 'add' of undefined

[MaestroJurko]

angular.js:10627
TypeError: Cannot read property 'add' of undefined
at resolveElementClasses (http://127.0.0.1:8282/js/Components/angular-animate/angular-animate.js:480:22)
at http://127.0.0.1:8282/js/Components/angular-animate/angular-animate.js:1028:27
at http://127.0.0.1:8282/js/Components/angular-animate/angular-animate.js:469:22
at Scope.$digest (http://127.0.0.1:8282/js/Components/angular/angular.js:13164:36)
at Scope.$apply (http://127.0.0.1:8282/js/Components/angular/angular.js:13380:24)
at HTMLLIElement. (http://127.0.0.1:8282/js/Components/angular/angular.js:21434:23)
at HTMLLIElement.jQuery.event.dispatch (http://127.0.0.1:8282/js/Components/jquery/dist/jquery.js:4371:9)
at HTMLLIElement.elemData.handle (http://127.0.0.1:8282/js/Components/jquery/dist/jquery.js:4057:28) undefined angular.js:10627
Error: Cannot read property 'add' of undefined Object {exception: TypeError, cause: undefined}

[Narretz]

Please provide the context of this error, and a reproduction in a plunkr etc. Otherwise, we cannot assess this at all.

[caitp]

I can think of a few reasons why this could happen in code --- What happens is, ngAnimate attaches the cache object to the jquery expandostore, and if that expandostore gets deleted for any reason, the cache disappears. This could be related to jquery cloning an element without cloning its data/event handlers.

We'd have to see your code to be positive what's going on, but @matsko we should probably add a safety check in there to prevent throws

[MaestroJurko]

what would that safety check look like, so I dont get this errors any more?

[caitp]

it would look like not treating the cache as an object if we determine that it's falsy, basically --- probably would want to abort the animation if the cache vanished, too

[MaestroJurko]

I put and if (typeof cache !== 'undefined') then do .add || .remove

[abhikmitra]

Getting the same error. Is this issue being worked upon ?

[matsko]

@abhikmitra yes, the PR is here: #8958.

[Narretz]

This should be fixed in 1.3.0 / master, see #8958

Otherwise, feel free to reopen