Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AutoCompleteTextView duplicates token when navigating back to view (Android) #443

Closed
rdlauer opened this issue Dec 7, 2017 · 4 comments
Closed

Comments

@rdlauer
Copy link

rdlauer commented Dec 7, 2017

Tell us about the problem

On Android only (iOS works fine), if you add a token to your AutoCompleteTextView, navigate away from the view, and return to the view, the token will be there twice.

Which platform(s) does your issue occur on?

Android only

Please provide the following version numbers that your issue occurs with:

  • Progress NativeScript UI version: 3.2.0
  • CLI: 3.3.1
  • Cross-platform modules: 3.3.1
  • Runtime(s): 3.3.0

Please tell us how to recreate the issue in as much detail as possible.

  1. Clone this repo
  2. Perform the steps shown in this gif:

untitled

@VladimirAmiorkov
Copy link
Contributor

Hi @rdlauer ,

Thank you for reporting this to us. I can confirm that it is issue in the current version of the plugin. I am taking a look at it as we speak and update you once I have more information.

@rdlauer
Copy link
Author

rdlauer commented May 9, 2018

I finally got around to testing this after upgrading to 4.0 and nativescript-ui-autocomplete to 3.7.0:

✔ Component nativescript has 4.0.0 version and is up to date.
✔ Component tns-core-modules has 4.0.0 version and is up to date.
✔ Component tns-android has 4.0.1 version and is up to date.
✔ Component tns-ios has 4.0.1 version and is up to date.

I'm finding the exact same problem exists on Android, with the token being added to the display when navigating back.

@VladimirAmiorkov can you please re-open this?

@VladimirAmiorkov
Copy link
Contributor

Hi @rdlauer ,

I managed to reproduce this issue with the current version of nativescript-ui-autocomplete and I will reopen it. It looks like there is an additional issue that was not initially resolved leading to the same issue in additional scenarios.

@zbranzov
Copy link
Contributor

zbranzov commented Aug 8, 2018

The fix is released in nativescript-ui-autocomplete@3.8.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants