App fails in Web App Previews Portal and Open Build Service
complete
J
Jose Adolfo Villalobos
Back on November 21, 2021, we reported the bug described below. It has yet to be addressed. It is stopping the release of our application in web form. We shall truly appreciate if it can be resolved.
******
The project can be viewed correctly under the Android Preview and build, but is fails to view correctly in the Web App Previews or the Open Build Service.
Our pages have lengths exceeding the height of the viewing device (PC or tablet). To view these pages, we:
- Encapsulate the data in Scroll Views
- Use Stretch to the Viewport Height and Disable Scrolling
When the project is viewed in the Web App Preview, the pages are clipped to the bottom end of the page. Scroll views do not work.
Incidentally, we have a page where the user can dynamically request from the database a long list of data items. This page can expand to display correctly the long list and the page scrolls to the end.
******
As an additional problem,
buttons lose their text labels when viewed in the Web App Preview or are
compiled for distribution to the web. I have tried to compile using 3.4.10 and 3.3.5. The errors persist.
If you wish to view the app, the app ID is 375926
Thank you for your help solving this problem.

Log In
T
Timo Kapanen
complete
T
Timo Kapanen
Hi Jose Adolfo Villalobos, sorry for not coming back to this ticket earlier. I checked you app and can see, that you have now working builds. We have made few changes to the builder along the way.
How is the button issue? Pekka analyzed that earlier, was that helpful?
Best Regards, Timo Kapanen
T
Timo Kapanen
Closing this ticket now as there are working builds. If there is still an issue with button text, please create a new ticket.
P
Pekka Aaltonen
Hi,
I investigated the issue with the button label. We cannot check the exact situation in the screenshot as fetching data requires a valid authentication token.
However, state would be consistent with the button label being empty. The label is bound to the formula
UPPERCASE(data.getBlog.etiquetaBoton)
. Does the issue reproduce if the button has static text (for debug purposes) or is bound directly to the property instead of with a formula? My suspicion is that either the property is empty for one reason or another, or there is a rendering issue with the scrollview + data variable + formula interaction.
BR,
Pekka
T
Timo Kapanen
under review
T
Timo Kapanen
Hi Jose Adolfo Villalobos and sorry for not addressing your earlier ticket promptly. There is a potential issue with scrollviews which could be helped the following way. You need to specify the height for the scroll view → change the dimensions to advanced →
width: 100%; flex-grow: 1
. Hopefully this helps you to move forward. About the second issue with button text. We had a similar type of an issue last week which was fixed in market place component update. Could you check that all the new component updates have been installed and if the problem still exists. Best Regards, Timo Kapanen
J
Jose Adolfo Villalobos
Timo Kapanen:
Thank you for your prompt response. I will follow your instructions to solve the scrollview and report the results to you. Regarding the problem of the disappearing button text, i have installed all updates, but the problem subsists.
J
Jose Adolfo Villalobos
Hi, Timo. I followed your instructions for specifying the scroll view settings and the app now works well in the web. Thank you. Now i have the following questions:
- Are these changes to Advanced dimensions a permanent solution to the problem of the clipped list, or is it a temporary solution?
2. Are these settings going to affect the compilations of the app under iOS and Android?
In this respect, compiling my app for Anroid is failing. The error log is just a long list of messages that, quite frankly, is just gibberish. I don't understand it at all. Is there somewhere within AppGyver i can go to get some guidance to resolve the problems? One on the error messages says: “BUILD FAILED in 1m 42s Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. I don’t even understand what this means. I Will greatly appreciate your help.