Catch up wih the Appery.io community on our forum. Here you'll find information on the lastest questions and issues Appery.io developers are discussing.
https://forum.appery.io/
Hello Andrew!
Could you share your app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a and tell us steps to reproduce?
Hi Maryna,
It's already shared (I sent a support mail about the issue). Just open the app in the Test view, or in the Appery test app on your android, and you'll get a popup with the error on the initial page. But if you hit the refresh button on that page - which calls the same service - it works fine.
Regards,
Andy
Thank you! Could you remind app name?
PromoteYourCharity.
Hi Andrew,
Could you please also share your script?
Done - sorry, I'd not realised the scripts had to be shared separately.
Hi Andrew,
Please try removing all codeconsole.log()/code from your code. It doesn't affect the results so you don't need it. This should speed up the code execution.
Ah, thanks Katya! Removing the console.log() statements has resolved the specific problem I was having on page load
So... back to the original question I raised - I'd still like an answer on whether the original 300ms rule applies, or whether this has been removed.
I can't find anything about any burst limits on the pricing pages, or the appery.io terms and conditions page.
Regards,
Andy
Hi Andrew,
We will update our pricing page soon. So, on your question:
Restriction : script burst rate (launch interval):
ul
liStarter : 300 ms;/li
liStandard : 125 ms;/li
liPro : 100 ms;/li
liPremium : 50 ms;/li
/ul
In other words, server side scripting is not useful for any scalable application. Better just for testing and limited use case scenarios.