-
Notifications
You must be signed in to change notification settings - Fork 681
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
Issues Are Auto-Closed Due to Inactivity Even When Unresolved #1628
Labels
suggestion
New feature or request
Comments
This was referenced Nov 13, 2024
Closed
I have the custom picker issue as well |
This issue is stale because it has been open for 7 days with no activity. |
This issue is stale because it has been open for 7 days with no activity. |
Lol |
This issue is stale because it has been open for 7 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi flutter_file_picker team,
I've noticed that many issues on this repository are being automatically closed due to inactivity, not because they are resolved. This practice makes it difficult for users to suggest improvements or report bugs because issues get closed prematurely, leading to lost feedback and unresolved problems.
Whenever I try to suggest a solution or raise a concern, the issue eventually gets closed if there's no activity. Additionally, I’ve found dozens of issues mentioning the same problem, and they are all closed due to inactivity—not because a solution was provided. This system creates a frustrating experience, as valid issues are swept away without resolution or proper acknowledgment.
Please reconsider Auto-Closing Policies
The text was updated successfully, but these errors were encountered: