extensions: unable to use rezised images through public url

Implementation/fix details are being discussed. Once a decision has been made, I’ll update this issue… Thanks for your patience!

+1 to this. I have not found a convenient way to make the resized images publicly accessible without doing manual post-processing with additional cloud functions.

The generated thumbs have no access token visible in Firebase console, there is no clickable link to view the images, and the preview of the image never loads (infinite spinner).

I would expect that either:

(1) there exists a simple transformation from the original firebase storage URL to access the resized images (e.g., something you could hardcode in client logic), or (2) this firebase extension comes with documentation describing how to best post-process the resized images to make them accessible

this fix worked for me https://stackoverflow.com/questions/59072882/cloud-functions-resized-images-not-loading/61023298#61023298

Just FYI, I’m following along on this thread. I’m hoping a solution is found soon. Thanks

+1 to this. I have not found a convenient way to make the resized images publicly accessible without doing manual post-processing with additional cloud functions.

The generated thumbs have no access token visible in Firebase console, there is no clickable link to view the images, and the preview of the image never loads (infinite spinner).

I’m facing the same issue… Seems kind of pointless at the moment to use this extension at all.

Thanks everyone! I think we pushed a commit last week that fixed this. Please let us know if you continue to see issues!

Hello,

No news ? 😃

@dackers86 lets reevaluate where we are on this

I have found the solution to it like i have to comment out the line which deleting the access token in the cloud function and now i have access to token of image after resizing but there is problem that if i have to change the configurations of extension the code is updated in cloud function so i have to change this line every time i change the configuration. this solution works for me well but its not a solid solution.

its simple process

1. after installing the extension go to functions
2. then select view details usage its opens a screen from where you have to select source
3. form source find file named FUNCTIONS/LIB/INDEX.JS , Go to line 152 then comment this out code on line 152 : delete metadata.metadata.firebaseStorageDownloadTokens;

Yeah the PR is especially considerate, to even ask the user if they want to delete the token. But pretty sure can just remove that one line

delete metadata.metadata.firebaseStorageDownloadTokens;

And everyone can finally use this extension. Unless maybe someone does need to hide their thumbnails, but not the originals? (Seems like that would be a rare use case.)

Thanks for the contribution @sitefinitysteve, the reason why we took so long was because we didn’t realize that the issue was simply that we should not be deleting the download token from the metadata. Thanks for providing the helpful Stackoverflow link @K0EZ !

Submitted a PR to block the delete based on a config option, no idea if it’ll get approved though…

How is this not fixed yet, I thought this extension solved all my avatar issues. But without the tokens it’s useless.

The solution from @K0EZ worries me if the function code gets somehow gets updated by Firebase on a new version?

Feels like a no brainer to just make this a config option in the extension options…? Who has the usecase to automatically generate resized images you can’t use?

EDIT Looks like this just happened to me, the cloud function code changed and reverted to what it was where it deleted the commented out line. Seriously need a fix…

Why is this here without being configurable https://github.com/firebase/extensions/blob/master/storage-resize-images/functions/src/index.ts#L203

+1 waiting for a fix

On Tue, 31 Mar 2020 at 20:26, QuentinSc notifications@github.com wrote:

Hello,

No news ? 😃

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/firebase/extensions/issues/140#issuecomment-606679532, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRLL6H4ITQNE6PTZQAASXTRKIADJANCNFSM4J5BQBPA .

The documentation explains that if no rule expression is provided, the rule evaluates to true. I see now. Thank you.

Happy to close this issue as completed as this feature is available now starting from v0.1.29 we have a config option to make images public that can be toggled during installation or by updating the extension config.

Feel free to reopen it if you still have issues with it

Hi @devth @felix-lambert

I’ll reopen this issue for investigation.