Forum | Appery.io

Hi,

I have the following problem. I want to start my database service (which populates mobile list component) upon page show event. But when I use "Invoke service" on page show event the scoll of returned list is choppy and slow. When I check the console I see that my service keeps sending request to database and returns the following info:

Resource interpreted as Image but transferred with MIME type text/html: "http://appery.io/404.htm".

When I launch the same service upon button click event such problem does not appear and the scroll is smooth.

How to remedy this?

My app is called "3mamcukier" and is shared with Appery support.
You can reproduce this by clicking in my app the last tab on the navbar called "Ulubione".

Hi Adam,

Please share your application with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a
On what page/service can I see this?

My app is called "3mamcukier" and is shared with Appery support.
You can reproduce this by clicking in my app the last tab on the navbar called "Ulubione".

One more thing. To see that list first you must add some items (they are stored locally). Open the page called "Baza". Expand "Grupa" and then pick any category you like. You will be given the list of articles. Each article has a gray star icon. Click on it on several different articles and they will be added to the list in question.

Hello Katya,
I was able to figure out what is wrong.
On my start page i have the same service attached to the Collapsible component. In this component there is an event "Expand" upon which the service is triggered. For some reason collapsibles "do not like" when they are left with "collapsed" unchecked (looks like there is some kind of loop). So I keep them collapsed but accidentaly I left this one it in "expanded" state and saved my project. At the same time I have my app rendered as a single page, so this issue also affected the page called "Ulubione".
Finally, once I have checked "collapsed" the problem is gone...
Nevertheless it might be worth checking why collapsibles behave like that.

Adam,

Thank you for the update! Glad it's solved.