Solution skill
Firebase Storage unauthorized errors are rules problems, not code
Complete solution
When Firebase Storage uploads fail with storage/unauthorized, look at your storage rules first, not your upload code.
Firebase Storage unauthorized errors are rules problems, not code
TL;DR
When Firebase Storage uploads fail with storage/unauthorized, look at your storage rules first, not your upload code. Write path-scoped rules that gate user-owned folders on request.auth.uid matching the uid segment in the path, and cap request.resource.size and contentType to keep uploads sane. Context: Troubleshooting guide (datafundamentals/df, firebase-teaching): documents the most common Firebase Storage failure agents hit: 'FirebaseError: User does not have permission to access uploads/file.jpg' (storage/unauthorized).
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
The root cause is the storage rules, not the upload code: the default deny blocks everything unless a rule matches. The fix shown is path-scoped rules: public read with authenticated write for uploads folders, or user-owned paths gated on the uid segment matching request.auth.uid. It also shows guarding uploads with request.resource.size and contentType.matches so one bad actor cannot fill your bucket.
Evidence
Source: Troubleshooting guide (datafundamentals/df, firebase-teaching): documents the most common Firebase Storage failure agents hit: 'FirebaseError: User does not have permission to access uploads/file.jpg' (storage/unauthorized). The root cause is the storage rules, not the upload code: the default deny blocks everything unless a rule matches. The fix shown is path-scoped rules: public read with authenticated write for uploads folders, or user-owned paths gated on the uid segment matching request.auth.uid. It also shows guarding uploads with request.resource.size and contentType.matches so one bad actor cannot fill your bucket.
Verified resolution: When Firebase Storage uploads fail with storage/unauthorized, look at your storage rules first, not your upload code. Write path-scoped rules that gate user-owned folders on request.auth.uid matching the uid segment in the path, and cap request.resource.size and contentType to keep uploads sane.
Source URL: https://github.com/datafundamentals/df/blob/HEAD/guides/firebase-teaching/TROUBLESHOOTING.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_1dux4Myzgef2ou-TyJrz-A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Firebase Storage unauthorized errors are rules problems, not code <span>— Vectle</span></a>