Subsequent search produce no result

[organik1]

Expected behavior

After receiving the result of one search, carrying out a subsequent search should be possible.

Actual behavior

Subsequent app search produces a blank list.

How to reproduce

• Launch Apktrack
• Locate the Search icon at the top of the screen
• conduct first search. Input a keyword and hit enter on your keyboard.
• clear keyword, input another keyword and hit enter.

Testing Environment

• Browser: CHROME
• Operating system: Android v6.0 (marshmallow)
• chipset: spread
• App Version: v2.1.3

Recording Of The Bug

---

Posted on Utopian.io - Rewarding Open Source Contributors

---

[JusticeRage]

Hi! Thanks for the report.
I believe this is expected behavior: subsequent searches are performed on the list currently displayed (at least, that's what happens when I try to reproduce the issue). So for instance, if you perform a search for com., a few packages should be displayed, and any subsequent search will only sift through those results.
If you want to start a new search, you need to click the back arrow first.

Can you confirm that this is what happens on your device?

[organik1]

Absolutely. That's what happens

…

On Monday, April 2, 2018, Ivan Kwiatkowski ***@***.***> wrote: Hi! Thanks for the report. I believe this is expected behavior: subsequent searches are performed on the list currently displayed (at least, that's what happens when I try to reproduce the issue). So for instance, if you perform a search for com., a few packages should be displayed, and any subsequent search will only sort through those results. If you want to start a new search, you need to click the back arrow first. Can you confirm that this is what happens on your device? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#130 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aij1fG7Qnyyzy-l2PDUo1_rXsJEeRcyxks5tkjp6gaJpZM4TDdk2> .

[JusticeRage]

Okay then. I'll be closing this report as "expected behavior" then. Thanks for taking the time to report it though!

[organik1]

I'm glad I could help.