FirebaseExtended / FirebaseExtended/reactfire

403 on storage request

Offen
#565 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
v5
Vorherrschende Sprache
TypeScript
Sterne
3.6k
Forks
403
Ø Merge
14 Std. 53 Min.
Gemergte PRs (30 T.)
5

Beschreibung

### 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

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
firebase, react, typescript
Bereich
cloud, frontend
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.