Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
fkskirer
Contributor II
Contributor II

Qlik Sense Mobile Error- Keyboard Disappearing

I came across an error that occurs using the Qlik Sense Mobile app that causes the mobile keyboard to disappear or crash when trying to search in a filter pane. I've found that if you open a filter pane that is at the bottom of the screen and you try to search the list box.. it causes the keyboard to glitch and not appear as it should.

I've tested this a few times and these are the circumstances that seems to trigger it:

  • Occurs both when using the Mobile app & using Qlik via a web browser like Safari or Chrome 
  • This bug occurs when the Filter pane is located towards the bottom part of the sheet (whereas triggering the mobile keyboard to open would cover the filter you are trying to use) 
  • Happens regardless if Extend sheet is active or not
  • Only occurs when using the search function in the filter pane, otherwise the filter opens with no issue 
  • I've also found that it occurs more often when the mobile device is being viewed landscape (I was testing both an iPad & iPhone)

I've attached a video demonstrating what I'm talking about. In the video you can see I am attempting to open the filter 'Customer #/Name' located at the bottom. The filter originally opens just fine, but when I click to try and search- the mobile keyboard attempts to open but then crashes. I try this x3 in the video and all 3 times it happens. At the end of the video I attempt the same thing using the filter at the top of the sheet 'Product Family'... and it works just fine so this bug only happens when the filter is placed towards the bottom of the sheet.

So I'm looking for potential solutions. Our user base really likes to have all of their filters located down the side of the sheet so I would prefer to not move all the filters to the top. Maybe there is something in the iPad settings that could be changed to fix this? Any help would be greatly appreciated.

-Steve  

 

 

Labels (1)
1 Solution

Accepted Solutions
ofer-wallach
Former Employee
Former Employee

Hi Steve,

As Viney said, thank you for bringing this issue to our attention. The development and Quality teams are aware of this issue, and it is being tracked on our systems. The development team had still not addressed the issue due to prioritization, but hopefully, it would be addressed sooner than later.

Regards,

Ofer

View solution in original post

6 Replies
Vinay_Kapoor
Employee
Employee

Hey Steve,

 

Thanks a ton for bringing this to our attention. I am sending it to the dev team to see if they have encountered this issue and if there is a fix already on it's way.

 

Regards,

Vinay

ofer-wallach
Former Employee
Former Employee

Hi Steve,

As Viney said, thank you for bringing this issue to our attention. The development and Quality teams are aware of this issue, and it is being tracked on our systems. The development team had still not addressed the issue due to prioritization, but hopefully, it would be addressed sooner than later.

Regards,

Ofer

bettinas
Contributor
Contributor

Hi Ofer,

we have the same issue and we're looking for possible solutions as well. 

Would be great when this issue would get fixed soon since our users primarly work on the iPad. 

Best,

Bettina 

ofer-wallach
Former Employee
Former Employee

Hi Bettina,

Thank you for reaching out and confirming that you are too seeing the same issue. I will pass the information in our proper channels to make sure our Dev team is aware it is impacting users more widely than previously known/expected. Hopefully, both your input as well as Steve's would help to put some more priority on fixing this and other related issued.

Best regards,

Ofer.

fkskirer
Contributor II
Contributor II
Author

Thank you Ofer and Vinay. We really appreciate the quick response and feedback 

fkskirer
Contributor II
Contributor II
Author

I see this bug was fixed in the recent June 2019 update. Thank you Qlik!! 

clipboard_image_1.png