Open DevKursat opened 2 months ago
This is an important bug. Can you let me know when it is resolved and I will send a new update? @hariprasadms
I will send an update today. Is it possible to fix the error today, please? @hariprasadms @takashiff @asmengistu @organicnz
When there is no initial value, there must be an empty set
Can you please solve these errors quickly? They are not difficult mistakes, but they are very important. I will launch an advertising campaign where I expect an average of 10K to 100K downloads of my app. I'm waiting for you team please! Thank you from now @hariprasadms @takashiff @asmengistu @organicnz
Has the error been resolved? Should I send an update? I can't test the Apple device... @hariprasadms
Has the error been resolved? Should I send an update? I can't test the Apple device... @hariprasadms
I'm having the exact same issue! I noticed it only occurs in long dropdowns, with more than 10 items.
DropDown contains 81 items. Is it resolved? . I will submit an update to Apple. I can't test it. (I'm using Windows.) If you're on a Mac, can you test this on a real device, please? @matheuspina
DropDown contains 81 items. Is it resolved now? . I will submit an update to Apple. I can't test it. (I'm using Windows.) If you're on a Mac, can you test this on a real device, please? It crashes in DropDown containing 11 items, I think the reason is in the initial value section.
My users keep bothering me, come on team please! @matheuspina @hariprasadms @takashiff @asmengistu
There is a new update. Has this bug been resolved?
We are experiencing the same issue. Can someone please tell us if this has been fixed in the latest release of FlutterFlow? This crashes our entire app and has led to customer complaints!
We are experiencing the same issue. Can someone please tell us if this has been fixed in the latest release of FlutterFlow? This crashes our entire app and has led to customer complaints!
He left me in a difficult situation too.
Also confirmed and discovered this issue also. Anyone know of any temporary workarounds?
Also confirmed and discovered this issue also. Anyone know of any temporary workarounds?
I think you should add initial value but it worsens the user experience in my application, so I'm waiting.
Can someone at FlutterFlow please respond to this bug? It is causing a complete application crash for all of our users when interacting with a drop-down box. Please can you provide an update on when this will be looked or a work-around? @hariprasadms @takashiff @asmengistu @organicnz
Can someone at FlutterFlow please respond to this bug? It is causing a complete application crash for all of our users when interacting with a drop-down box. Please can you provide an update on when this will be looked or a work-around? @hariprasadms @takashiff @asmengistu @organicnz
My users have been giving me a headache for almost a week. It doesn't seem like a very difficult mistake, but I guess the team didn't care yet...
Can someone at FlutterFlow please respond to this bug? It is causing a complete application crash for all of our users when interacting with a drop-down box. Please can you provide an update on when this will be looked or a work-around? @hariprasadms @takashiff @asmengistu @organicnz
Confirm for me, is your dropdown in a component or in a custom dialog? I noticed that i only had this bug when i loaded a long dropdown in a component or custom dialog
Can someone at FlutterFlow please respond to this bug? It is causing a complete application crash for all of our users when interacting with a drop-down box. Please can you provide an update on when this will be looked or a work-around? @hariprasadms @takashiff @asmengistu @organicnz
Confirm for me, is your dropdown in a component or in a custom dialog? I noticed that i only had this bug when i loaded a long dropdown in a component or custom dialog
It crashes both when you dropdown directly on the page or when you dropdown within the component.
Hi @DevKursat, I apologize for the delayed response. I've done some testing, and I'm currently unable to reproduce the issue. If possible, could you provide a blank project in which the issue can be reproduced? This will greatly help us in finding the root cause of the issue and deploying a fix. Thank you
Hi @DevKursat, I apologize for the delayed response. I've done some testing, and I'm currently unable to reproduce the issue. If possible, could you provide a blank project in which the issue can be reproduced? This will greatly help us in finding the root cause of the issue and deploying a fix. Thank you
Please test this project on a real iOS device. https://app.flutterflow.io/project/zafer-rqs8we?tab=appSettings&appSettingsTab=mobileDeployment https://apps.apple.com/us/app/kürşat/id6466145956?src=AppAgg.com
Also, the update I just sent appears to have been queued for 8 hours.
Could you please let me know as soon as you fix the error? Otherwise my users might kill me @takashiff
Can someone at FlutterFlow please respond to this bug? It is causing a complete application crash for all of our users when interacting with a drop-down box. Please can you provide an update on when this will be looked or a work-around? @hariprasadms @takashiff @asmengistu @organicnz
Confirm for me, is your dropdown in a component or in a custom dialog? I noticed that i only had this bug when i loaded a long dropdown in a component or custom dialog
For us we see this in a custom component which is displayed in a bottom sheet. We load the dropdown options from a custom function which returns a list of strings. Note 'Is Searchable' is turned on and 'Fix Position' is turned on. It seems from the code that Is Searchable loads a different module dropdown_button2. Flutterflow team may want to check that the stable version of this has been included and not the prerelease beta!
One option may be to disable search to see if it actually loads the standard Flutter dropdown instead.
Crash happened in dropdowns having many items exactly!
The problem is either nullable or localization. But please fix it now so we can send an update. @hariprasadms
Hi, I have the same problem. The issue is only on the iOS version (works perfectly on Android). The dropdown widget is located within a drawer, It is populated from a constant which contains a list of 10 items. Please help and fix asap. thanks
Hi, I have the same problem. The issue is only on the iOS version (works perfectly on Android). The dropdown widget is located within a drawer, It is populated from a constant which contains a list of 10 items. Please help and fix asap. thanks
I have been shouting for more than a week, but the team does not care about such a big mistake...
Since I don't have a Mac device, I sent a new update thinking that maybe it was solved, I explained it in the notes, they agreed that you should check these dropdowns, but the error still persists, I'm about to go crazy, why does Apple approve a crashing application, and how can a big and reliable company like Flutterflow not solve the error that crashes the application for more than a week? What could be more important? MY APPLICATION IS CRASHING! @mixart @matheuspina @hariprasadms @michaelyom @cnickel76
NEW UPDATE: https://apps.apple.com/tr/app/k%C3%BCr%C5%9Fat/id6466145956
You are right. I wonder why this issue is not reported by more users. Did you think of replacing the regular dropdown widget with a similar custom widget (one downloaded from pub.dev for instance). I think it is the only way out for now....
On Mon, Mar 25, 2024 at 2:04 AM DevKursat @.***> wrote:
Since I don't have a Mac device, I sent a new update thinking that maybe it was solved, I explained it in the notes, they agreed that you should check these dropdowns, but the error still persists, I'm about to go crazy, why does Apple approve a crashing application, and how can a big and reliable company like Flutterflow not solve the error that crashes the application for more than a week? What could be more important? MY APPLICATION IS CRASHING! @mixart https://github.com/mixart @matheuspina https://github.com/matheuspina @hariprasadms https://github.com/hariprasadms @michaelyom https://github.com/michaelyom @cnickel76 https://github.com/cnickel76
— Reply to this email directly, view it on GitHub https://github.com/FlutterFlow/flutterflow-issues/issues/2547#issuecomment-2017034927, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNLREYZDRIMWSSDPDO62QLYZ5ZZTAVCNFSM6AAAAABE2XT5QSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGAZTIOJSG4 . You are receiving this because you were mentioned.Message ID: @.***>
I give up, I'll use ChoiceChips in the component instead of dropdown... @mixart @matheuspina @hariprasadms @michaelyom @cnickel76
ok let me know if it works better on iOS...
On Mon, Mar 25, 2024 at 10:31 PM DevKursat @.***> wrote:
I give up, I'll use ChoiceChips in the component instead of dropdown... @mixart https://github.com/mixart @matheuspina https://github.com/matheuspina @hariprasadms https://github.com/hariprasadms @michaelyom https://github.com/michaelyom @cnickel76 https://github.com/cnickel76
— Reply to this email directly, view it on GitHub https://github.com/FlutterFlow/flutterflow-issues/issues/2547#issuecomment-2018954369, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNLRE6PZJU5W6DID7XXEXDY2CJTRAVCNFSM6AAAAABE2XT5QSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYHE2TIMZWHE . You are receiving this because you were mentioned.Message ID: @.***>
It didn't work as I thought, this error needs to be resolved now, team, where are you, it's been a week! @mixart @matheuspina @hariprasadms @michaelyom @cnickel76
Does this mean the problem is not the dropdown widget as such?
I think the error was in the fix position. I sent a new update but it has not been approved yet.
Can you be more precise? What do you mean fix position? Please let me know if it really works. Best,
Le mar. 26 mars 2024, 15:14, DevKursat @.***> a écrit :
I think the error was in the fix position. I sent a new update but it has not been approved yet.
— Reply to this email directly, view it on GitHub https://github.com/FlutterFlow/flutterflow-issues/issues/2547#issuecomment-2020546497, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNLRE7MKUI3EZKJOGQVCFLY2F7DTAVCNFSM6AAAAABE2XT5QSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGU2DMNBZG4 . You are receiving this because you were mentioned.Message ID: @.***>
The error was not due to Fix Position. I beg the team to fix this mistake, it puts me in a very difficult situation! @mixart @matheuspina @hariprasadms @michaelyom @cnickel76
same problem here, big problem for me too
@hariprasadms @takashiff Is this error difficult? Can you please solve it?
Hi @DevKursat, we are currently working on this issue, but are still unable to reproduce it on our own systems, making it hard to debug. If possible, could you provide a blank project where this issue can be reproduced? This will expedite the bugfixing process. Thanks
what do you mean a blank project?
Hi @DevKursat, we are currently working on this issue, but are still unable to reproduce it on our own systems, making it hard to debug. If possible, could you provide a blank project where this issue can be reproduced? This will expedite the bugfixing process. Thanks
Take a bottom sheet, add a dropdown with a least 50 items and you should have the bug on a real ios17 iphone
Hi @DevKursat, we are currently working on this issue, but are still unable to reproduce it on our own systems, making it hard to debug. If possible, could you provide a blank project where this issue can be reproduced? This will expedite the bugfixing process. Thanks
Unfortunately, the project crashed on iOS and I tested it on Windows, but you can view it from my project.
Project ID: zafer-rqs8we Code for a faulty widget: ITEeyfLl05NPn7xJ16X1LccwmQMwJFg2a+Y/p+0aRQ0hfZysOqQhPeCkP1BLYtefTFY3BU2jhkYD0fzvkvPTDfUpAEyuQaJjyZRXQRXgWlGiMJiyPqiWXWpAM9tnGH6g1p+J2CV4IuluL2AC3FOtfvCdG3qCf9qOYwx5e6fDbOY=
@takashiff @hariprasadms This insistence is not really for pleasure. It is much more important than the errors in the Windows application, because while using the Windows application is a choice (I installed it, but I am still working from the web, for example), this error prevents the use of my application. (If the initial value is [] instead of null when the initial value is empty, it may work as well as before, but you are the masters of the job, of course, it has been almost 2 weeks, please, but I need action now, my users are very upset with me.)
Hi @cnickel76, by blank project I mean a project where the issue has been reproduced and there is nothing else in the project. For example, in this case, a blank project would be a project that contains only a dropdown that causes the app to crash, and nothing else (and any specific configurations necessary that causes the dropdown to crash). Hope this explanation helps
Hi @DevKursat, I understand your frustrations in that this issue is taking longer than intended to be resolved. We are currently still in the process of debugging the issue, and I will keep you updated. Once our engineering team is able to reproduce the issue and find the root cause, I will let you know, as then we will be able to fix the bug. Thank you for your patience and understanding.
Hi @DevKursat, I understand your frustrations in that this issue is taking longer than intended to be resolved. We are currently still in the process of debugging the issue, and I will keep you updated. Once our engineering team is able to reproduce the issue and find the root cause, I will let you know, as then we will be able to fix the bug. Thank you for your patience and understanding.
What are the working hours? I wonder if it will be completed before the end of this month? (I'm glad I got your attention :))
In my case my dropdown is only ten items but still crashes. Items come from a list stored as app constant. The app crash at the moment the dropdown unfolds.
Le mer. 27 mars 2024, 17:09, drpark @.***> a écrit :
Hi @DevKursat https://github.com/DevKursat, we are currently working on this issue, but are still unable to reproduce it on our own systems, making it hard to debug. If possible, could you provide a blank project where this issue can be reproduced? This will expedite the bugfixing process. Thanks
Take a bottom sheet, add a dropdown with a least 50 items and you should have the bug
— Reply to this email directly, view it on GitHub https://github.com/FlutterFlow/flutterflow-issues/issues/2547#issuecomment-2023159427, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNLRE3FYICXSEDJV3OPDC3Y2LOLVAVCNFSM6AAAAABE2XT5QSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTGE2TSNBSG4 . You are receiving this because you were mentioned.Message ID: @.***>
Hi all, I have tried testing on an iPhone running iOS 17.3.1, but I am still unable to reproduce the issue despite testing the various configurations mentioned. If possible, please provide a blank project where I can easily reproduce this error so that our team can more quickly find the cause of the issue. Thanks
Hi all, I have tried testing on an iPhone running iOS 17.3.1, but I am still unable to reproduce the issue despite testing the various configurations mentioned. If possible, please provide a blank project where I can easily reproduce this error so that our team can more quickly find the cause of the issue. Thanks
You can test it in my project. I shared the project ID, let me share it again. Project ID: zafer-rqs8we Component error when sharing post URL: https://app.flutterflow.io/project/zafer-rqs8we?tab=widgetTree&component=GonderiHazirla (Kategoriler widget) Page fault when filtering event URL: https://app.flutterflow.io/project/zafer-rqs8we?tab=widgetTree&page=AnaSayfa (sehirrr widget)
As long as the error is resolved as soon as possible :))
@takashiff We have created a blank project for you with a searchable Dropdown including 20 options. This should be enough to reproduce the error. Project ID: drop-down-crash-ty7nsl Please keep in mind this only crashes when you have deployed it to a real iOS device. So you cannot duplicate the issue with test or web or Android builds. You will need to get this built and deployed to an iPhone or iPad to reproduce the crash.
Bug Report Code: IT48lMjfsIhgod9G0M+MbfoxhjgWQ207bZ0W0e1Hbws8J5zbPbN/eP/RPxFuZrynTGxUeVmjkT401vfquIfPF8A4NS6bRpxh/7V+cAzJQkCuMJSKCs27fW1QL+5VGBGb5sCvqhUlIsxsS0447V2qNu+9QnbrHozQOlcwRfK1KdeK2SrDX1iXc2URm05KZDPz
it crashes too without searchable dropdown on my side
it crashes too without searchable dropdown on my side
I think the issue is in the initial value part.
Has your issue been reported?
Current Behavior
When you select a few items on Apple, it kicks out of the app
Expected Behavior
As in the old update, the user can choose or not choose what he wants and the application should never crash (if the DropDown value is empty, all items should be shown)
Steps to Reproduce
No problem on Android or Web. You need to check iOS. (I cannot test it on the emulator because the Windows application is not released yet. You can use the currently released version to test it.)
Reproducible from Blank
Bug Report Code (Required)
ITEeyfLl05NPn7xJ16X1LccwmQMwJFg2a+Y/p+0aRQ0hfLLyOrNzOc7SVxZLYteWe3x+Iln/oHkewPDIvYfDLfpdCyiubr5MwZRXQRXgWlGiMJiyPqiWXWpAM9tnGH6g1p+J2CV4IuluL2AC3FOtfvCdG3qCf9qOYwx5e6fDbOY=
Context
I want my app not to crash on apple it left me in a very difficult situation with my users
Visual documentation
https://github.com/FlutterFlow/flutterflow-issues/assets/141324500/a31d0174-3c88-4704-8aab-37eaba9ead2e
Additional Info
Project URL: https://app.flutterflow.io/project/zafer-rqs8we?tab=widgetTree&component=GonderiHazirla
Environment