May 3, 20224 yr Great work with the UI-revamp of the new 6.8! While long-pressing Enpass in the launcher and tapping "Search","New" or "favorites", Enpass opens but doesn't focus on the search bar nor bring up the keyboard like it did before. It just goes to the main view Edited July 5, 20232 yr by Ivarson Fixed
May 4, 20224 yr Hi @Ivarson, Thank you for reporting the presence of this issue. I have shared it all with the concerned team for further investigation. In the meantime, we highly appreciate your patience with us. SI-2781
May 23, 20223 yr Author Actually it's only partially fixed. The shortcuts has been refined and now triggers views in the main app, however the Search-shortcut only highlights the search-bar and shows the previous searches, it doesn't "focus" the search-bar, which would bring the keyboard up. Hence, it's still needed to tap "Search" again in order to start typing. That way there's no point having a shortcut. So let's call the .Focus() on the searchbar when search-shortcut is pressed.
May 24, 20223 yr Hi @Ivarson, I appreciate your response and I have shared your feedback with the concerned team for further investigation. In the meantime, your patience is highly appreciated here.
May 31, 20223 yr Author On 5/24/2022 at 12:41 PM, Manish Chokwal said: Hi @Ivarson, I appreciate your response and I have shared your feedback with the concerned team for further investigation. In the meantime, your patience is highly appreciated here. After some further testing, the issue occurs when using Microsoft Swiftkey as keyboard. When using the default Gboard, the keyboard pops up.
June 2, 20223 yr Hi @Ivarson, We were able to reproduce this issue with your assistance, and the concerned team is working on fixing it. In the meantime, we highly appreciate your patience with us.
February 14, 20233 yr Author This issue has come back for me, that is, the keyboard isn't triggered when tapping "search". Enpass 6.8.6 768 Android 13 Google Pixel 7 Neither SwiftKey nor Gboard "pops up" (previously only SwiftKey had this issue)
February 15, 20233 yr Hi @Ivarson Thank you for sharing the feedback related to this issue. I shared your comments with our dedicated team, and upon a thorough investigation, we were able to reproduce the bug. Our development team is now working on fixing it as a priority, and a patch addressing this issue will be released soon. We appreciate your kind patience and cooperation in the interim.
Create an account or sign in to comment