We are currently working on fixing the scrollable column/screen in web app. We took a look at your web app Could Note, and itâs a complex app that we are not sure if we identify your issue correctly.
Is it possible for you to provide an app that only includes the scrollable issue you are facing?
No⌠Am I dumb lol I know how to add a pwa to the homescreen Iâm speaking about: Imagine I send the pwa to clients⌠where and how should they know that thexy can add it to the home screen.
There should be a external popup like would you likt to add the app if yes it shows how to add it
Our staff inspected your app and found that you may have turned on the scrollable property on the screen component, but you may need to turn on the scrollable property for the column component as well. The attached picture show where the scrollable property in the column component is.
Mobile web app issue with text box: Iâm experiencing this problem too. On android, text box cannot be filled. The keyboard drops. This problem is not presented on iOS or MAC Book. Kindly look into it.
@rollke Iâm not 100% sure but I think itâs the same as unpublishing your mobile web apps. Iâll look into this for you.
Just FYI though, if you unpublish and the republish a mobile web app the URL stays the same. (Iâm guessing youâre thinking about using these as examples in your books?)
I am also waiting for this to be fixed, i have an app ready for release but on hold because of this issue, No app security if you cant login. This is a vital thing that needs urgent attention. i do not want to have to rebuild my app for a third time due to components not working as intended, it is rather tiring. Do we have some sort of time frame for when this will be rectified. @domhnallohanlon. Normally i dont complain about things like this as i can usually figure a workaround eg. like i did with app subscription, but i managed it. This issue however there is no workaround for and needs to be addressed ASAP. PLEASE THUNKABLE FIX THIS ISSUE. LOGIN PAGES ARE USELESS IN A PWA WITHOUT THIS FUNCTIONING PROPERLY.
I understood from previous discussion with eoinparkinson & point that its possible to set permanent redirect to thunk.app/web-build/⌠, but for a custom web app, it would be really awesome to have the URL in the browser itself to be consistent with Brand / Domain a user has visited.
To clarify conclusion on custom domains, I would like to confirm whether its possible to just show the web URL in the browser to be
I think the idea would be to have the url still show our custom url even though it redirects to the thunk.app URL. Could this be possible if we register our domain with thunkable. Can you force a pointing url to show?
Top Tab Navigator is bunched up so the text is on two lines instead of one - again this reflects on the unrealistic screen-size.
Frankly itâs a mess and I expected better. You could even make the phone look realistic, to make it feel like an actual app (or have an option for that).
Also, it would be nice to be able to embed this, so it can be easily white-labelled.
Buttons donât even seem to work unless the ânavigate to screenâ is put first (I had a vibrate and then web API to POST before navigating, which didnât work), meaning I have to change around a load of blocks just to get it working as a web-app, hugely inconvenient.
It would be almost fine if it worked, but itâs basically unusable . Sorry.
No need to apologies, thanks for your candid feedback @hdawc, weâre always looking to grow and improve our product.
Correct still in beta, but your feedback, and the 100 or so other comments above this, help make it better and get us ever closer to a stable release.
Have you been looking at this in a web browser on your Computer? Iâd highly recommend opening it on your phone as this was, initially at least, the intended use case.
Youâre actually the first person to have raised this issue, well spotted. Looking at your article it might be an easy fix, can you open a ticket on Github for this please and lets see if we can get this resolved!
Can you share a screenshot of this please? Again, does the issue persist when tested on a physical device?
A number of our fantastic community members have already asked for this and itâs on the way. Thereâll be an announcement when it goes live.
This does sound strange - was there an issue here because itâs asynchronous or do you think its a bug? If itâs a bug please file a ticket on Github, please let me know if you need any help with this.