phath9
phath9
Found this error as well, any update?
Having similar issue. The problem arises when I tried to putFile to storage but no problem when accessing file. The emulator will abruptly stop without giving any meaningful info.
It seems to be related to storage rules. From my testing, only `allow read, write: if true;` works. Any other complex rules will break the Emulator. Maybe related to https://github.com/firebase/firebase-tools/issues/3550....
> This may be related to #4470 and long file paths. > > My storage rules are already set to `allow read, write: if true;` but I am still encountering...
It happens with Android as well. Guess there's something inherently wrong with headerBytes. When headerBytes is given, it will always return mime type associated with the given headerBytes, no matter...