You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey not sure if this is the best place to reach out. Loving this extension but I am running into an issue with the caching.
Steps to Reproduce
Upload file to Firebase Storage to users/userID/profile-pic.jpg
Use invertase process api to get the image on the client
Upload a new profile picture to users/userID/profile-pic.jpg
Once again, use invertase process api to get the image on the client
Issue
I am getting back the original upload picture (from step 1) not the newer picture (from step 3). I believe this is because Invertase is caching the photos (which is great), but how can I skip/update the cache when I know that the picture has changed?
Potential Solution
Somewhere in the input could there be a bool parameter skipCache where Invertase would skip the cache and get the new image?
Or is there a different API other than GET /process that we can hit to let Invertase know the cache is invalid?
I hope this makes sense! Happy to provide more details & have been loving this extension -- thanks for all the hard work!
The text was updated successfully, but these errors were encountered:
Hey not sure if this is the best place to reach out. Loving this extension but I am running into an issue with the caching.
Steps to Reproduce
Issue
I am getting back the original upload picture (from step 1) not the newer picture (from step 3). I believe this is because Invertase is caching the photos (which is great), but how can I skip/update the cache when I know that the picture has changed?
Potential Solution
Somewhere in the input could there be a bool parameter skipCache where Invertase would skip the cache and get the new image?
Or is there a different API other than GET /process that we can hit to let Invertase know the cache is invalid?
I hope this makes sense! Happy to provide more details & have been loving this extension -- thanks for all the hard work!
The text was updated successfully, but these errors were encountered: