Rating plugin not working on iOS and Android app
I am using RateIt (https://rateit.codeplex.com) plugin to show star ratings. Plugin is working fine on desktop browsers and appery.io tester app but not on iOS and Android apps.
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/
I am using RateIt (https://rateit.codeplex.com) plugin to show star ratings. Plugin is working fine on desktop browsers and appery.io tester app but not on iOS and Android apps.
Hello,
What exactly doesn't work? Could you check are there any errors in console? This (https://devcenter.appery.io/documenta...) should help.
Hi Sergiy,
Thanks for responding. The debugger is a really neat tool. We'll use it more often. The problem still persists. The plugin is not displaying any stars (greyed out or otherwise) when viewed from certain devices.
The debugger does not show any errors in the console. I tried the debugger when running the app from both the Desktop browser (where I am able to view the star rating) and from the mobile appery app on an android (where I don't see the stars). In looking at the css elements, It almost seems like the css file (rateit) for the plugin is not being loaded in the instances where the stars don't show up. Here are the different contexts we tried...
Desktop - Chrome browser - Works
Mobile - Android - Using Appery.io tester - Does not work
Mobile - Android - Using Chrome browser - Works
Mobile - Android - Using native app - Does not work
Mobile - iOS - Using Appery.io tester -Works
Mobile - iOS - Using the native app - Does not work
Please help.
Hi Shankar -
Could you please explain with details how you have implemented this plugin into Appery.io project?
Or you can provide us with app public link that we can check in the browser.
Hi Illya,
I sent you a the link privately. When I tried the app today, it is working. We made no changes. I am assuming you had an opportunity to fix whatever was causing this issue. We can close this issue for now.