View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013362 | MMA | General | public | 2016-06-15 15:23 | 2019-11-07 10:30 |
| Reporter | marek | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 1.2.0 | ||||
| Target Version | 2.1.0 | ||||
| Summary | 0013362: Deal somehow with storages with no space left | ||||
| Description | Currently the storages are considered as writable and it might fail on creation of storageInfo.xml. This way the storage is not used in MMA at all. It should be somehow managed. | ||||
| Additional Information | https://rink.hockeyapp.net/manage/apps/66872/app_versions/166/crash_reasons/124897639 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Can you elaborate on this? Doesn't sync/wi-fi sync reserve space according to the setting in MMW? |
|
|
Yes, sure. But the storage might be full due to other applications and MMA will fail to even create the storageInfo.xml file. This way the storage is considered as faulty and it is not used. There are a few options. 1. We can consider it as readonly, this refuse all syncs 2. we can probably consider it as writable. But USB sync won't work correctly...due to missing storageInfo.xml |
|
|
Why not go with 2. but also notify the MMA user? e.g. Upon starting MMA, if storageinfo.xml is missing due to space constraints and if this message hasn't appeared the previous time that MMA has run: 'Warning: your device is running low on storage and any attempt to sync will not work correctly. To resolve, free up at least 100 MB.' |
|
|
This is a good way. But maybe we can use combination with 1. because I am worried about unexpected behaviour. I.e. show the notification warning and consider storage as readonly till resolved by user. This will avoid failures during syncs and the writability will be recovered right after some space will be freed. |
|
|
Sure sounds good. So upon failed creation of the file: 'Warning: your device is running low on storage. Please free up at least 100 MB in order to sync.' Note: if this issue applies to all storage locations, then the logic would probably have to be implemented selectively, and the message would have to be changed to: 'Warning: Please free up at least 100MB in order to sync:" <location 1> <location 2> |
