-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data Rendering issues in ScrollableTabBar
#1815
Comments
|
It is possible that the tabs in a scrollabletabbar are all being rendered at the same time. @sharjeelyunus please provide an example |
@kmahmood74 try here on Android, its actually noticeable on web as well: https://studio.ensembleui.com/app/JV3Jtf6e2yCfiYZD8R5t/screen/AI3Kl4m9vzlO4gx1mbF2 Email: [email protected] |
yes I can see it on the web as well but there isn't a lot of content |
I added the firebase crashlytics, and these are the errors I'm getting
|
@snehmehta can we prioritize this? getting a lot of rendering issues, and no workaround for now |
@snehmehta this is urgent, customer app is crashing alot, can you please fix this issue asap? |
Just tested it with the new build, it is still crashing the app. PS: we are just updating a storage variable on navigating back of screen, this works on any other screen where we don’t have scrollable tabbar CC: @kmahmood74 @sharjeelyunus @snehmehta ScreenRecording_01-24-2025.15-40-53_1.mp4 |
The code looked good to me, freezing issue was bcz we are loading too much data at the same time, tried following solution on my end:
Recording with loading tabs one by one. |
The
ScrollableTabBar
tends to freeze a lot, especially on Android. On iOS, the freeze only lasts a few seconds (mostly not noticeable), but on Android, it can sometimes freeze for over a minute, especially when there's a lot of data. This problem gets worse when you have more content in the tab bar. The whole point of using the ScrollableTabBar is to handle large amounts of data easily.REF: https://discord.com/channels/1031982848485359626/1306327142895718401
The text was updated successfully, but these errors were encountered: