A FocusNode was used after being disposed

[eyoeldefare]

A FocusNode was used after being disposed

[eyoeldefare]

Apologize for

@eyoeldefare thank you so much, please let me know if you push an update. Keep doing great work mate!

Hi! Did you able to use the package later? or use any other package?

Hey sorry about that. I am working on it. I will have a new version out before this saterday that will fix this. Also with major updates to make this package super customizable.

[eyoeldefare]

Seems like I should have left that for users to call dispose on it instead of doing that internally. I will fix it soon

[eyoeldefare]

This is what I suspected.
You guys are calling dispose on the TextEditingController property in your own component class. Why would you do that? You know the TextFieldTags widget is taking your controller as a parameter. We're disposing all properties we take in as parameters inside the widget so no need to dispose of it from your side.

[motasimfuad]

I will keep this open to see if this issue persists.

Thanks man!

[fokoz]

@eyoeldefare thank you so much, please let me know if you push an update. Keep doing great work mate !

[motasimfuad]

Got stuck on this issue. :/

[motasimfuad]

@eyoeldefare thank you so much, please let me know if you push an update. Keep doing great work mate!

Hi! Did you able to use the package later? or use any other package?

[eyoeldefare]

@eyoeldefare thank you so much, please let me know if you push an update. Keep doing great work mate !

Hey sure. I think I have enough free-time now to really work on this package and make it somehow production grade package. I will push a major fix and upgrade to the overall package before Saturday.

[abdugaliyev]

Damn, i get this error...

[Nish1312]

Hey @eyoeldefare... Getting the same issue... Is there any temporary solution until you fix this??

[eyoeldefare]

Hey yeah, last version doesn't have this issue. You can downgrade till this saterday.

[abdugaliyev]

Hey yeah, last version doesn't have this issue. You can downgrade till this saterday.

downgrade doesn't help

[Nish1312]

Hey yeah, last version doesn't have this issue. You can downgrade till this saterday.

Hey yeah, last version doesn't have this issue. You can downgrade till this saterday.

downgrade doesn't help

It worked in my case. Thanks @eyoeldefare .

@abdugaliyev make sure you are not using '^' with package version while downloading.

[eyoeldefare]

I will keep this open to see if this issue persists.

[parsadoc]

I downgrade the package to version 1.4.2 and it works for me

...
 textfield_tags: '1.4.2'
...

[gorkemsari]

Any updates?

[jerrypaulsam]

Any updates?

[eyoeldefare]

This was solved as far as I see. What issues are you guys experiencing in this regard?

[jeprojects]

@eyoeldefare Getting this when using with RawAutocomplete:

A TextEditingController was used after being disposed.

The error stack is pointing to your dispose method in the controller:

textEditingController!.dispose();

[eyoeldefare]

Hey @jeprojects what version of the package are you using?
Also what version of flutter are you using?
From my understanding, this issue was solved almost a year ago.

[jeprojects]

@eyoeldefare
Flutter 3.3.5
textfield_tags: ^2.0.2

[eyoeldefare]

Can you please post example of the code you've used. I want to know why you're seeing this. This was happening last time because the component was being destroyed before an asynchronous operations was finished that utilizes internal methods.

[RoyalCoder88]

Hi friends, have the same issue with A TextEditingController was used after being disposed.

Only on the Autocomplete example, did someone fix this issue?
Thanks in advance!

[Luckey-Elijah]

This is what I suspected.
You guys are calling dispose on the TextEditingController property in your own component class. Why would you do that? You know the TextFieldTags widget is taking your controller as a parameter. We're disposing all properties we take in as parameters inside the widget so no need to dispose of it from your side.

this violates a common practice of allowing the component responsible for creating, also be in charge of closed/destroying.