🐛 Bug Report: Inconsistent Storage Permissions for Android vs. iOS

### 👟 Reproduction steps When setting storage read permissions to “Users”, file downloads work on iOS but fail on Android with a 404 Not Found error. However, if I temporarily switch the read permission to “Any”, save it, then switch it back to “Users”, the file downloads correctly on Android. This suggests a bug in how Appwrite handles permissions, potentially caching them incorrectly or not recognizing authenticated Android users properly. Steps to Reproduce 1. Upload a file to Appwrite Storage (I used a zip file and a json file). 2. Set read permissions to “Users” (not “Any”). 3. Try to download the file using Expo’s FileSystem.createDownloadResumable(). 4. On iOS, the file downloads successfully. 5. On Android, the request fails with a 404 error. 6. Workaround: Temporarily set read permissions to “Any”, save, then switch back to “Users”, and save again—now Android works too. ### 👍 Expected behavior Android should recognize authenticated users just like iOS does, without requiring a manual permission toggle. ### 👎 Actual Behavior **Response headers from failed request (Android):** { "status": 404, "headers": { "Content-Type": "application/json; charset=UTF-8", "X-Debug-Fallback": "true" }, "uri": "file:///data/user/0/host.exp.exponent/files/no.zip" } **Possible Cause** This could be a caching issue in Appwrite’s ACL system or a bug in how Android users are authenticated under the “Users” scope? **Additional Context** I originally reported this on Discord weeks ago but haven’t seen a resolution yet. Would appreciate any insights :-) ### 🎲 Appwrite version Version 1.6.x ### 💻 Operating system MacOS ### 🧱 Your Environment **Appwrite Version: 1.6.1** **Platform: Android (Expo SDK, React Native)** **Expo SDK Version:** "expo": "~52.0.35", "expo-av": "^15.0.2", "expo-checkbox": "^4.0.1", "expo-file-system": "~18.0.10", "expo-font": "~13.0.1", "expo-linking": "~7.0.5", "expo-media-library": "^17.0.6", "expo-ro…