Uncaught TypeError: Cannot read property 'dispose' of undefined about i18n HOT 14 CLOSED

ok I can't actually replicate the issue but have talked to @jdanyow to update aurelia-plunker to include it so you can easily create a sample. Stay tuned will reply here once its updated

from i18n.

@valichek / @zewa666 sorry for the delay- the plunker has been updated with the latest aurelia bits and now includes the aurelia-i18n plugin.

http://bit.ly/aurelia-plunker

from i18n.

I have the same issue, I have trouble to pinpoint where the actual problem is and are thus unable to show it in plunkr.

    Unhandled promise rejection TypeError: Cannot read property 'dispose' of undefined
        at TCustomAttribute.unbind (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/t.js?bust=1448609338856:118:26)
        at Controller.unbind (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:2724:20)
        at View.unbind (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:841:26)
        at ViewSlot.unbind (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:1137:21)
        at View.unbind (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:846:23)
        at ViewFactory.returnViewToCache (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:1731:14)
        at View.returnToCache (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:753:24)
        at removeAction (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:1246:25)
        at ViewSlot.removeAll (http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:1259:7)
        at http://localhost:1111/jspm_packages/github/aurelia/[email protected]/aurelia-templating.js?bust=1448609338856:3653:53(anonymous function) @ :1111/jspm_packages/npm/[email protected]/modules/es6.promise.js?bust=1448609338856:122
    :1111/jspm_packages/npm/[email protected]/modules/es6.promise.js?bust=1448609338856:122 Unhandled promise rejection TypeError: Cannot read property 'dispose' of undefined(…)(anonymous function) @ :1111/jspm_packages/npm/[email protected]/modules/es6.promise.js?bust=1448609338856:122

from i18n.

hey we currently have weird issues with the show.binding if used together with the animator-css. May I ask you guys to test if the error still happens if you remove the animator-css plugin?

from i18n.

I have aurelia-animator-css plugin disabled

from i18n.

sry I seem to be doing something wrong, still can't replicate the issue. @valichek may I ask you to use the updated aurelia plunker to create an example depicting the issue?

from i18n.

@zewa666 will try

from i18n.

I wonder if there's a scenario where bind then unbind is called in the same task queue flush. If that were to happen, unbind would be called before this line is evaluated.

Maybe this could be reproduced by putting a t custom attribute on a element that has if.bind="show" and then executing this.show = !this.show a few times in the view-model.

It might be good to clear these timeouts in unbind:

• https://github.com/aurelia/i18n/blob/master/src/t.js#L49
• https://github.com/aurelia/i18n/blob/master/src/t.js#L61

Otherwise there is the potential for the deferred binding code to execute after unbind is called.

from i18n.

Any progress with this? You should clear these timeouts during unbind and run dispose() of subscription only if really subscribed.

from i18n.

@EisenbergEffect could you create a new release and @valichek check it afterwards? I guess @Mordred's PR should fix that

from i18n.

We will have some new releases this week. Hopefully tomorrow or Wednesday. I'm waiting on a couple of final things to come in so we can aggregate the patches and release details.

from i18n.

@valichek has this been fixed with the recent release?

from i18n.

yes, error is gone

from i18n.

Allrighty 👍

from i18n.