Choice chips names are not visible.

[Aktivitele]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Sometimes the choice chips' names are visible, and sometimes they are not. For example, when first entering the main page, they are visible, but after an instant reload, the names do not fully appear. When I test it on a mobile device with the APK, the names are visible upon the first login, but when switching to another app and returning, the choice chips' names do not fully appear.

Expected Behavior

For the choice chips' names to always be visible

Steps to Reproduce

"Log in,
the main page will open,
then perform an instant reload,
observe the encountered error

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4gl8qB249Im+EA7qrAde9WqD84JlA4aIc0t94bSQ4YGJTyD+wuf87eSERWXc/kTFFtM2H9o2oW0tKKid/hA8AEaCWBbNg4z4dqWDzgQTmgVraDFJWgdXJSO/tQf0C/08GJgBNCXbFvR1Fl2WD3Bt6+Tj/DO7rSOG0kDq/LZO4=

Visual documentation

WhatsApp.Video.2025-02-14.at.16.23.11.1.mp4

Environment

FlutterFlow v5.2.1 released February 14, 2025
Flutter version is 3.27.3

Browerser:
Version 133.0.6943.99 (Official Build) (64-bit)

Windows 11 Home 
Android 11

Additional Information

The main component of my project displays something based on categories. For a better user experience, the choice chip names should be scrollable in a single row. Therefore, it is quite important to see the choice chip names fully

[Alezanello]

Hello! 👋

We recently encountered a similar issue, which was caused by a specific layout applied to Choice Chips. You can follow the discussion and potential solutions here: GitHub Issue #5162.

[Aktivitele]

Hi, I followed the instructions exactly, but nothing has changed unfortunately, it's still not working

…

On Mon, Feb 17, 2025 at 7:40 PM Ale Zanello ***@***.***> wrote: *Hello!* 👋 We recently encountered a similar issue, which was caused by a specific *layout applied to Choice Chips*. You can follow the discussion and potential solutions here: GitHub Issue #5162 <#5162>. — Reply to this email directly, view it on GitHub <#5436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOD2SPTGBNRS6PN2XTYXVNT2QIGIXAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGYYTMNBZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: Alezanello]*Alezanello* left a comment (FlutterFlow/flutterflow-issues#5436) <#5436 (comment)> *Hello!* 👋 We recently encountered a similar issue, which was caused by a specific *layout applied to Choice Chips*. You can follow the discussion and potential solutions here: GitHub Issue #5162 <#5162>. — Reply to this email directly, view it on GitHub <#5436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOD2SPTGBNRS6PN2XTYXVNT2QIGIXAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGYYTMNBZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Aktivitele]

Even when I clone the project on the page and try it myself, it still doesn't work. It just displays the ChoiceChips names with ellipsis On Wed, Feb 19, 2025 at 7:13 PM Aktivitele < ***@***.***> wrote:

…

Hi, I followed the instructions exactly, but nothing has changed unfortunately, it's still not working On Mon, Feb 17, 2025 at 7:40 PM Ale Zanello ***@***.***> wrote: > *Hello!* 👋 > > We recently encountered a similar issue, which was caused by a specific *layout > applied to Choice Chips*. You can follow the discussion and potential > solutions here: GitHub Issue #5162 > <#5162>. > > — > Reply to this email directly, view it on GitHub > <#5436 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BOD2SPTGBNRS6PN2XTYXVNT2QIGIXAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGYYTMNBZG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > [image: Alezanello]*Alezanello* left a comment > (FlutterFlow/flutterflow-issues#5436) > <#5436 (comment)> > > *Hello!* 👋 > > We recently encountered a similar issue, which was caused by a specific *layout > applied to Choice Chips*. You can follow the discussion and potential > solutions here: GitHub Issue #5162 > <#5162>. > > — > Reply to this email directly, view it on GitHub > <#5436 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BOD2SPTGBNRS6PN2XTYXVNT2QIGIXAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGYYTMNBZG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[Alezanello]

Hello again!!

Do you mean this project?
https://app.flutterflow.io/project/qa-3342-ciw9lp

[Aktivitele]

Yes ,I do The project URL here is: https://app.flutterflow.io/project/aktivitele-7h1fpi?tab=pageSelector&page=HomePage credentials ***@***.*** 123456 for login

…

On Thu, Feb 20, 2025 at 5:51 PM Ale Zanello ***@***.***> wrote: Hello again!! Do you mean this project? https://app.flutterflow.io/project/qa-3342-ciw9lp — Reply to this email directly, view it on GitHub <#5436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOD2SPXGFHFAEZAWDVCDZP32QXTWLAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRG4ZDQOJTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: Alezanello]*Alezanello* left a comment (FlutterFlow/flutterflow-issues#5436) <#5436 (comment)> Hello again!! Do you mean this project? https://app.flutterflow.io/project/qa-3342-ciw9lp — Reply to this email directly, view it on GitHub <#5436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOD2SPXGFHFAEZAWDVCDZP32QXTWLAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRG4ZDQOJTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Aktivitele]

I think if you check the video in github you will understand exact problem On Thu, Feb 20, 2025 at 5:54 PM Aktivitele < ***@***.***> wrote:

…

I am sending two different videos: one from a real device and one from FlutterFlow. On a real device, when a user logs in for the first time, the *ChoiceChip names are fully visible*. However, after minimizing and reopening the app, *the ChoiceChip names are not fully displayed*. When navigating to another page and returning, they appear correctly again. In FlutterFlow, after an *instant reload*, the *ChoiceChip names are also not fully visible*. But after navigating to another page and returning to the home screen, they display correctly On Thu, Feb 20, 2025 at 5:52 PM Aktivitele < ***@***.***> wrote: > Yes ,I do > The project URL here is: > > https://app.flutterflow.io/project/aktivitele-7h1fpi?tab=pageSelector&page=HomePage > > credentials > ***@***.*** > 123456 > > for login > > On Thu, Feb 20, 2025 at 5:51 PM Ale Zanello ***@***.***> > wrote: > >> Hello again!! >> >> Do you mean this project? >> https://app.flutterflow.io/project/qa-3342-ciw9lp >> >> — >> Reply to this email directly, view it on GitHub >> <#5436 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/BOD2SPXGFHFAEZAWDVCDZP32QXTWLAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRG4ZDQOJTG4> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> [image: Alezanello]*Alezanello* left a comment >> (FlutterFlow/flutterflow-issues#5436) >> <#5436 (comment)> >> >> Hello again!! >> >> Do you mean this project? >> https://app.flutterflow.io/project/qa-3342-ciw9lp >> >> — >> Reply to this email directly, view it on GitHub >> <#5436 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/BOD2SPXGFHFAEZAWDVCDZP32QXTWLAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRG4ZDQOJTG4> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[Alezanello]

I’ve confirmed the issue—I'll escalate this to the engineering team for a fix. Thanks for bringing it to our attention!

[Aktivitele]

I hope They might fix the issue .We are waiting for any news about the issues

…

On Thu, Feb 20, 2025 at 10:02 PM Ale Zanello ***@***.***> wrote: I’ve confirmed the issue—I'll escalate this to the engineering team for a fix. Thanks for bringing it to our attention! — Reply to this email directly, view it on GitHub <#5436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOD2SPXO5DFU3I4OZA7F2ZL2QYRFRAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGQYTMOJSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: Alezanello]*Alezanello* left a comment (FlutterFlow/flutterflow-issues#5436) <#5436 (comment)> I’ve confirmed the issue—I'll escalate this to the engineering team for a fix. Thanks for bringing it to our attention! — Reply to this email directly, view it on GitHub <#5436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOD2SPXO5DFU3I4OZA7F2ZL2QYRFRAVCNFSM6AAAAABXIYVGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGQYTMOJSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>