-
My goal:
Use native Container, Icon and Text components to create small colored labels that fit their contents, sit horizontally together, and wrap as whole containers when space runs out.
-
Issue:
On Android, containers holding icon/text combinations expand across the available row and stack vertically. The same layout stays compact on iPhone. I’m seeing this across Android models and versions.
These aren’t dedicated badge/tag components—just styled native containers.
-
Steps I've taken to troubleshoot:
I created Ignite Layout Lab A8, a sample-only reproducer using literal data and no database queries. In its Badges tab, compare:
-
B20: One Text in a content-sized Column—correct on both platforms.
-
B22: One Icon in that Column—correct on both.
-
B21/B23: Two Text components in a Row—expand on Android, compact on iPhone.
-
B13/B24: Icon + Text—same Android expansion.
B21 reproduces it without an icon or an extra inner container. Changes to wrapping, growth settings and icon rendering haven’t resolved it reliably.
One Mobile HTML component rendering the complete strip works as a temporary workaround, but I’d prefer native components.
-
-
Additional info:
Retool Cloud. Screenshots compare the same A8 tests on Android and iPhone. The sample-only A8 JSON export is included.
Is this a known native container-sizing issue, or is there a supported configuration I’m missing?
Also am getting an error when i try to attach screenshots but have them if needed Ignite layout lab.json (347.1 KB)
Summary
On Retool Mobile (Cloud), native content-sized/fit-to-content Containers holding an Icon + Text (or multiple Text components in a row) expand to fill the available row and wrap vertically on Android, while the same layout stays compact and hugs its contents on iPhone.
AI Response
After reviewing the Community forums and the Retool Mobile documentation, no existing report, documented supported configuration, or changelog entry was found that directly corroborates or resolves this specific Android-vs-iOS divergence in content-sized container width. The Mobile Container docs confirm that row (horizontal) layouts with Gap and Padding are supported, but they do not document a fit-to-content vs. grow width behavior or any platform-specific sizing difference, so they do not offer a reliable fix here. Given this, the single-HTML-component strip already identified remains the most reliable workaround for a consistent cross-platform result until this rendering difference can be confirmed and addressed. Because the connection of all other surfaced topics is only tangential, none are cited rather than risk pointing to unrelated material.
Sources
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a
,
, or
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. ![]()