Content
I received a report from an Android user (iOS works fine).
Issue:
When the user taps the text box to type a message, the Android keyboard appears but the screen does not move up. As a result, the keyboard completely covers the text input field and the user cannot see what they are typing.
Has anyone experienced this issue on Android before?
If you know the cause or how to fix it (e.g. settings like adjustResize / adjustPan, Adalo-specific solutions, or Android configuration), please let me know.
This keyboard overlap on Android is one of the most common issues I see, but I’ve got a fix that works every time without fail.
The cleanest way I’ve done it on all my chat and messaging screens:
Take the whole group with your text input and send button (that bottom bar), drop it inside a Rectangle container.
Then just make the rectangle taller than the screen, drag the bottom handle down so it extends off the visible area (Slightly below the edge is usually enough).
Set the rectangle to Sticky While Scrolling (Bottom position).
Once the keyboard pops up, Android sees that extra off-screen space and automatically pans the view so the input stays visible and you can type normally.
Thanks for the screenshots, the rectangle with Fixed to Bottom and extra height off-screen is the right setup for the legacy editor.
If users are still seeing the input covered, drag the rectangle bottom handle even lower (give it a lot more space below the visible area) and republish a new native build, that extra room is what makes Android adjust the view for the keyboard in legacy apps.
Another option that helps on message screens is using the (Enter Text Input) component from the Marketplace, it handles keyboard behavior more smoothly on Android native.
As a long-term solution, I would recommend moving to the new Adalo Responsive design (New Editor), that eliminates these legacy keyboard issues completely, as the adjustment is automatic there.
Extending the rectangle further should resolve it.
Since the extended rectangle didn’t fully resolve it in the latest build, try swapping the native Text Input for the (Enter Text Input) component from the Marketplace. It handles keyboard focus and adjustment more reliably in legacy native builds.
If that doesn’t do it, migrating the screen to the new (Responsive Editor) is the most effective long-term fix, keyboard behavior is handled automatically there, and no workarounds required.
If I switch to the Responsive Editor now, are there any downsides?
I have been using the Legacy Editor so far, so I’m concerned about potential issues such as new bugs, or existing backend logic not working as expected.
Also, how can I switch to the Responsive Editor?
I don’t see any button or option for this in the Legacy Editor.
And I’m happy to try the specific paid Input component you suggested as a workaround. However, I don’t think I should have to pay for it.
Reason: this is an Android keyboard/viewport behavior issue in the native app environment. The same screen/implementation works on iOS, and the problem appears only on Android. That strongly suggests the issue is in the Adalo native wrapper/editor behavior (or its interaction with Android), not in my app’s business logic.
Because the paid component is being used only to bypass a platform/runtime limitation, please cover the cost (or provide a free license/refund/credit for this component) so I can proceed without additional out-of-pocket expense.
If you agree, please tell me the best way to apply the credit or enable access for my account.
The main downside is the one-time migration effort, you might need to adjust the grouping and components alignments, so you restructure them in the new editor (backend logic like actions and collections stay the same, no bugs there in my experience).
Potential issues: Some legacy components might need to be changed, but it’s rare, and the new engine is more stable for native builds (fewer bugs overall).
How to switch: In the Adalo builder, go to the app settings → “Copy / Delete” → “Copy” → Change “Legacy App” “Mobile only” or “Responsive app” depending on your app’s layout. (Both are with the new editor).
The Enter Text Input was just an optional recommendation from me (many builders use it for better keyboard control in message screens), but it’s third-party, so pricing/credits are handled directly by the developer.
If you need any help with the migration or testing the component, feel free to DM me.
Besides Ali’s suggestions, if you check the PWA instead native build in an Android device, is it still same or working as expected? If I remember correctly, this bug existed in the past and not sure if that got fixed because haven’t tested legacy apps recently as was using responsive apps and this issue is not there like Ali mentioned.
I would suggest you to submit a support ticket and I’ll also double check with the team once they get back from holidays! : New Bug Form
Thanks for the detailed explanation on the Responsive Engine, @Ali-Bazzi. I appreciate you taking the time to outline the trade-offs and migration steps.
Before moving forward, I’d like to clarify one important point.
If this Android keyboard issue is caused by the Adalo platform (specifically the native wrapper and Legacy app behavior), then asking the app developer to personally cover the cost of a paid third-party Input component as a workaround would be unreasonable.
So before discussing paid components or alternative inputs, I’d like to clearly establish the root cause and responsibility for this issue in this thread first.
Here are the confirmed facts so far:
The same screen and implementation work correctly on iOS
The same screen and implementation work correctly on Android PWA
I tested the suggested workaround of extending the Rectangle container fully to the bottom of the screen, but the issue still occurs in the Android native build
Similar issues have been reported multiple times on the Adalo forum, where on Android native builds the keyboard appears but the screen does not move up, causing the input field to be covered (with reports noting that this does not occur on iOS)
On the Google / Android OS side, there are no official reports or acknowledgements of this issue as a known Android OS–level bug
Based on these facts, this does not appear to be an app-side logic or layout issue, but rather something specific to Android native behavior in the Legacy environment.
With that in mind, I’d like to clarify:
Is this a known or expected limitation/bug on the Adalo side (Legacy + Android native)?
Or is there evidence that this is caused by app-side implementation?
Once this is clear, I think we can decide on the most appropriate and fair next step.
As I mentioned in my reply to @Ali-Bazzi just before, I’ve already confirmed that the issue does not occur on Android PWA and only happens in the Android native build.
I also submitted a support ticket three days ago and am currently waiting for a response. Since this issue is affecting users, I appreciate the prompt and thorough support from your side.
