FirebaseExtended / FirebaseExtended/reactfire

403 on storage request

Open
#565 2 comments 0 reactions 0 assignees View on GitHub
v5
Dominant language
TypeScript
Stars
3.6k
Forks
403
Avg merge
14h 53m
Merged PRs (30d)
5

Description

### Version info

**React:** 18.2.0

**Firebase:** 9.15.0

**ReactFire:** 4.2.2

**Other (e.g. Node, browser, operating system) (if applicable):** chrome

### Test case

### Steps to reproduce

1. Upload a file to storage using useStorageTask
2. show that image with a
3. Remove that image with a deleteObject request.
4. Upload a different image with the same name to the same path
5. reactfire requests the file with the wrong access token and the request fails

### Expected behavior

The correct token is used to display the image from storage

### Actual behavior

An old token is used and the request fails

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the five-step sequence using useStorageTask, StorageImage, and deleteObject with Firebase 9.15.0. Trace how StorageImage obtains its access token after deleting and replacing a file at the same path. Done means the replacement image request uses the current token rather than the old one.

Written by the indexing model from the issue text.

Assessment

Tech stack
firebase, react, typescript
Domain
cloud, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.