mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #6815] [Bug] Free storage errors contradict information in the settings #3012
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3012
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @genseirin on GitHub (Nov 17, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6815
Originally assigned to: @appflowy on GitHub.
Bug Description
When trying to add more images, I repeatedly receive error messages that free storage was used up. Deleting old content and removing them from the trash doesn't help, even after restarting the app and clearing the cache I can add at most one more image and the problem reappears.
According to the information in "Plan" in my settings, however, I am well below the storage limit and never used any AI.
How to Reproduce
I don't know if it is a reproducible issue, but I might have crossed a certain threshold in data size or the number of elements.
Expected Behavior
Either the information about storage usage should show that I hit the limit, or it should be possible to add more images.
Operating System
macOS 14.7.1
AppFlowy Version(s)
0.7.3
Screenshots
Additional Context
I'm using the AppFlowy Cloud.
@appflowy commented on GitHub (Nov 18, 2024):
Hi @genseirin,
Thank you for reporting it. I will take a look today
@appflowy commented on GitHub (Nov 18, 2024):
@genseirin What is the size of the file you tried to upload?
@genseirin commented on GitHub (Nov 18, 2024):
Thanks!
File sizes are between 3 and 4 MB, all are photos (jpg, file names are a date + time). The page now contains 8 images, an external link and text. There are some (I think 6) further pages.
@appflowy commented on GitHub (Nov 20, 2024):
Hi @genseirin . Can you try 0.7.4? I've updated the error message.
@genseirin commented on GitHub (Nov 20, 2024):
With 0.7.4 I see:

The last image had 5.7 MB, the one before below 4 MB. In the plans overview I see that file uploads can take up to 7 MB. So that's not per file? Or could there be a flaw in determining the sizes?
I remember that I before added a file of 17.8 MB (i.e. a video, but added as a file), but later removed it. Maybe this has triggered the alert and the app isn't aware of the fact that is has been removed already.
@appflowy commented on GitHub (Nov 21, 2024):
@genseirin Noted. The alarm might be triggered by your 17.8 MB image. Could you please send me your log file? (Discord or Email)
@appflowy commented on GitHub (Nov 23, 2024):
@genseirin I've fixed this bug. A new version will be released next week
@genseirin commented on GitHub (Nov 23, 2024):
Thank you!
@genseirin commented on GitHub (Nov 26, 2024):
Confirmed, fixed with v0.7.5