-
Notifications
You must be signed in to change notification settings - Fork 41
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
Multiple loading indicators in monument details view #178
Comments
Can I Work On It |
Assigned! |
Hey @mdmohsin7, I can see no activity going on this issue. Can you please assign me this issue? let's get it done. |
Assigned! Pls go ahead @karthik14344 |
Iam dn with #186 pr, Can you please assign it to me ? @mdmohsin7 |
There are two ways to solve this issue, Approach 2: Shimmer Effect I suggest going with the second approach as it is better for the user experience |
Hey @mdmohsin7 can I work on this issue, please assign! |
Let's go with the first approach now otherwise shimmer on a single screen would not look that good. @kareemabdeen feel free to open another issue to replace circular indicators with shimmers in all the screens where it makes sense Assigning this issue to @khushi-hura for now as @kareemabdeen already has an issue assigned! |
hey @mdmohsin7 can u assign this to me,i can work on this |
@aayaan758 I am working on this! |
@khushi-hura oh okay ... |
hey @mdmohsin7 I want your help regarding firebase issues after setup, my account is not a billing account and it is asking to setup billing account before using storage as per new policies of firebase! |
Hi, you'll have to add your payment details for now, dw you won't get charged. In coming weeks we will migrate over to pocketbase.io or supabase.com or appwrite.io |
I have successfully added my payment details but they are asking for prepayment of 1000 INR :( |
hey @mdmohsin7 is there anything we can do on the firebase setup issue as of now or should I wait for the organization to switch to supabase.com or appwrite.io...?? |
I can take over this issue if @khushi-hura is still encountering problems, since we have already spent a lot of time addressing it. @mdmohsin7 |
@khushi-hura, could you please provide more details about the issue you're currently facing? I'd like to help you complete your contribution until @mdmohsin7 decides on our migration strategy from Firebase. |
Hi @kareemabdeen yes I am still facing issues with using storage in firebase. |
I think you don't need to use the billing account, as we are using Firestore, not Cloud Storage. |
Ohh! Also I think that in September, firebase has been updated everything to its billing account Could u plz make a setup and let me know if everything is working fine without setting up a billing account? Then I will try doing it again with your help. |
@khushi-hura Have you enabed Firestore? |
hey @kareemabdeen thanks for helping me out. There was something wrong with the setup, now working fine with the app! |
Hey @khushi-hura , glad to hear the setup issue is resolved and the app is working fine now! You can check the MonumentDetailsViewMobile file, the issue with the double loading indicators should be there. Let me know if you need further assistance! |
hey @mdmohsin7 @kareemabdeen is this what fixes the issue? |
Hi @khushi-hura, It seems the issue occurs when navigating to the details page for the first time, where the initial state shows two loading indicators instead of one. To help identify and resolve this, please follow these steps:
|
@khushi-hura Could you please provide more details about state now for this issue ? |
Yes @kareemabdeen I am sorry, I was out for new year. Can I please get 3 more days? |
@khushi-hura |
hey @kareemabdeen I just identified that the code is managing _isLoading boolean variable to ensure the state and at the same time the bloc is also managing the state, both are using circularProgressIndicators() which is resulting in 2 of them. |
There are multiple loading indicators which appear in the monument details view of the app. Ideally there should only be one indicator for both the components.
The text was updated successfully, but these errors were encountered: