Double import storage issue: by default, importing a file via expo-document-picker saves the file in the app cache directory, which allows other app processes (e.g. the map server) to read it. ~unfortunately, if the item isn't removed from the cache, it essentially doubles the storage usage of an import (cache + map server db storage), which builds up quickly. users can intervene by going to the app settings in Android (note, not the in-app settings) and clearing the cache, but this clears the whole cache, which would affect other parts of the app (generally in less consequential ways). ideally, once we know an import has succeeded, we should remove the file from the cache to avoid this double storage issue~ EDIT: according to Expo docs, these cache files are temporary and the OS will attempt to clean them up automatically based on device storage, so maybe this double storage issue isn't as severe of an issue?
Delete map server timeout issue: there seems issue where deleting a map and waiting for the response causes the app backend server timeout time to expire. not sure why that would be blocking that server but because of it, the error screen appears as a result.
noticing that this only happens if i have multiple tilesets imported; i tried this after importing 8 mb and 143 mb tilesets. i noticed that the deletion response takes much longer when this is the case, which may indicate that either something crashed (but not visible in adb logs 🙃) or a really slow query.
Actionable items to make the map server more usable and stable:
Improve logging: both client-side and server-side. the latter would probably depend on doing within the dep itself (see https://github.com/digidem/mapeo-map-server/issues/75)
Double import storage issue: by default, importing a file via
expo-document-pickersaves the file in the app cache directory, which allows other app processes (e.g. the map server) to read it. ~unfortunately, if the item isn't removed from the cache, it essentially doubles the storage usage of an import (cache + map server db storage), which builds up quickly. users can intervene by going to the app settings in Android (note, not the in-app settings) and clearing the cache, but this clears the whole cache, which would affect other parts of the app (generally in less consequential ways). ideally, once we know an import has succeeded, we should remove the file from the cache to avoid this double storage issue~ EDIT: according to Expo docs, these cache files are temporary and the OS will attempt to clean them up automatically based on device storage, so maybe this double storage issue isn't as severe of an issue?Delete map server timeout issue: there seems issue where deleting a map and waiting for the response causes the app backend server timeout time to expire. not sure why that would be blocking that server but because of it, the error screen appears as a result.