Hi,
With our client, we could reproduce a curious problem with mobile phones (Android and iOS) :
In an Interface we have a parent dropdown (category) that is used to filter a children dropdown.Initially the children list contains all the items because the selection of the category is on -Select- (null).
1.1/ Nominal case:
- The first time we select a specific category (let's say -1-), we meet an issue : the children list contains all the items (filter does not work)- Then we select another category (-2-) : all works fine, the children list is well filtered- Then we select again the previous category -1- : all works fine, the children list is well filtered (18 items with scrollbars)
After this, the children is always well filtered (whatever the category selected).
If we close the Interface then re-open it, we can reproduce the issue.
1.2/ Alternative case: If we make a test with a category filter that retreives few children items (less than 10, ie : without scrollbar), the issue does not appear.
It may suggest that the issue is linked to the number of items of the list.
We have tested this issue on the mobile phone/OS versions below :
- iOS 15.6.1- Samsung Galaxy A3 (Version android 8.0.0).- Galaxy A41 - Android version 12- Galaxy A5 - Android version 8- Galaxy S8 - Android version 9- Galaxy S22 - Android version 12
2/ We have another issue but we could reproduce it only under old OS :
The Appian Query that returns our children list is designed using the DB "is_active" field filter (the query is designed to never retreive the inactive items).With this old phone, when we test the dropdowns we can see some inactive items appearing in the dropdown list.
Of course, the 2 Bugs described above never happend on Windows computers (the client is using 75% of Windows computer and 25% mobile phone).
He is using the latest 22.3 Cloud Appian version.
- Would you have any idea about the reason of these issues ?- Is there any way to test Appian Android/iOS specifically ?
Regards
Discussion posts and replies are publicly visible
I suggest to put this post into a support case.
Yes, of course, it has done by the client.
But I was curious to see if any of you have met these kind of issues...
I did not see this.
Keep in mind that any logic or query is always executed server-side. I would be extremely surprised when a query returns a different set of data depending on the end-user device.
Regarding the first issue. Do you have a minimal self contained example you could share?
Yes, I was very suprised too.
yes, I have began to make a self contained example, but I miss some time...
I will send you as soon as possible...
Just to confirm, is this occurring when the devices are offline or when they are online? Like Stefan said, I'd be surprised to see this issue occur when online, because the evaluation occurs on the server and all devices should contain the same behavior. However, if the evaluation is offiline it's possible there is a bug with offline mobile.
One other idea - is there any logic on the form that uses one of the mobile context functions like a!isNativeMobile()?
Peter, I can confirm that the test we've made yesterday with our client (each of us using our own telephone) was made online.
For the 2nd issue, thank you for the idea, I have to ask to the client if is it possible that the "is_active" issue could have occurred offline. -- EDIT: after asking the question, the mobile was online --
For your last point, I can confirm you that the a!isNativeMobile() function is not used.
We had a return from the support (the bug is confirmed). Here is their reply :
Hi there,We have some news from the product team. They have managed to reproduce the issue and are going to treat it as a bug (new reference for this is AN-215216)