Incorrect Error Message Displayed When Creating Project on Workspace with Reached Data Limit
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
No source file or test is named. Start by reproducing the workspace data-limit case and trace the project creation and sync error handling from that flow. The work is done when syncing a project at the limit displays “You have reached a data limit” instead of the generic project-creation error.
Written by the indexing model from the issue text.
Description
Summary:
When a workspace has reached its data limit, a user is still able to create a new project. Upon syncing, an unhelpful generic error message is displayed instead of informing the user that the data limit has been reached.
Workspace: storage_limit
Environment:
Staging [x] PROD [x]
Application:
Device/OS/APP: IPhone 15 / iOS26.5 / MM 2026.3.0 - 924211
Steps to Reproduce:
- Use a workspace that has reached its data limit (1.0 GB / 1.0 GB).
Workspace: storage_limit - Create a new project in the application.
- Hit upload - a modal window about insufficient storage is displayed.
- Open the project and attempt to sync the project.
- Observe the error message displayed.
Actual Behaviour:
A generic error message is displayed stating that the project could not be created and instructing the user to contact the support team ("Couldn't create the project. Please try again later or contact support if the problem persists.")
There is no reference to the data limit being the cause of the failure.
Expected Behaviour:
The application should display the same error message as shown in the data limit screen: "You have reached a data limit", clearly informing the user that the sync failed due to insufficient storage.
Screenrecord:
https://github.com/user-attachments/assets/a46aa2d9-9466-4c43-a67f-9a777f407446
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/mobile
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MerginMaps/mobile#4669 ·
-
bug Good first issue ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4665 ·
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/mobile#4647 · 1 comment ·
-
enhancement sync
MerginMaps/mobile#4713 · 2 assignees ·
-
enhancement performance qgis
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MerginMaps/mobile#4701 ·
All issues in MerginMaps/mobile
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·
-
Component: GLib
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Mute ydb/tests/functional/dstool/test_canonical_requests.py.Test.test_group_take_snapshot in main Openai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ydb-platform/ydb#53974 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·