-
Notifications
You must be signed in to change notification settings - Fork 4.4k
🐛 Bug Report: User total is zero (0) in project console after minor version upgrade #5628
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
Comments
👋 I will have to confirm this after doing another installation and upgrade. I just realised that there is a small chance that I have done the upgrade after adding no more users during the preceding 30-day time period. In that specific case, the So it could (of course) be a coincidence! I will try to confirm when upgrading one if our other Appwrite installations. Apologies if I just noticed a coincidence. |
Hi @wernerm any updates after upgrading? |
Yes, I could do another upgrade without reproducing the issue. It must have been a coincidental statistical period cut-off on my side. This issue can be closed. |
Hi @wernerm since you mentioned that it is working fine for you now, and we can close, I am closing it. Feel free to re-open or reach out on Discord, if you have any questions. |
👟 Reproduction steps
When I upgraded from version 1.3.3 to 1.3.5, the total amount of users in the "AUTH" summary block of my projects changed to zero (0).
Before the upgrade, it showed the correct total number of users in the project.
👍 Expected behavior
It should show the correct total number of users in the project. (It used to work fine before the update.)
👎 Actual Behavior
It displayed zero (0) after the update and continues to display zero (0) - this remains unchanged, even when adding or removing users from the project. The number does not change anymore after the upgrade. (It used to work fine before the update.)
🎲 Appwrite version
Version 1.3.x
💻 Operating system
Linux
🧱 Your Environment
This issue affects the Appwrite console.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: