unable to use rezised images through public url

[harshapulikollu]

[READ] Step 1: Are you in the right place?

Yes.

[REQUIRED] Step 2: Describe your configuration

• Extension name: _ (storage-resize-images)
• Extension version: _0.1.3

[REQUIRED] Step 3: I'm unable to access the resized images through a public(download) url from my flutter app, like I'm able to retrieve original image. I don't see any reason to use this extension if i can't access those resized images by manipulating the original Image URL.

please provide me a way how can I access those resized images from my flutter app.

[brandonpearcy]

+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

[NicolasMaas]

+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.

[TiagoGouvea]

Happening with me also. Works fine on "dev" project but not on "prod" project. Both projects has billing activated.

On my "dev" project, sending a new image trough firebase console or by code, it generates the public URL of the resized file.

• Resized image on dev project

On my "prod" project it don't work.

• Original file on prod project
• Resized filename: 4433b4d7-f058-4aae-8faf-ffd11c42a4dd_650x500.jpg
• Storage file: gs://guess-where-i-am.appspot.com/images/4433b4d7-f058-4aae-8faf-ffd11c42a4dd_650x500.jpg

The process full log:

A console print with infinite loading:

[smbowler]

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

[smbowler]

Hi @Ehesp, happy New Year. I just wanted to check-in to see if there was a solution to this issue. It seems to be the same issue presented in #155

My development team paused development on our own solution when we found the firebase photo-resizing extension, but are awaiting your response to these two issues before we dedicate time to implementing and debugging.

Any insight would be greatly appreciated. Thank you!

[lars-sorensen]

I am also wondering this. Also wondering about the lack response here...

[anthowm]

In my backend I generate signedUrls dont like this way but also is weird that in my frontend I need to delay the get of resized images because it return to me 404 if not delay it for 2000 (the next times to access to resized images works without delay...).
When the original file works like a charm with signedUrl ...

First call is original file the second is the resized:

for (const resizeFile of urisArray) {
          const bucketFile = this.storage.file(resizeFile);
          const result = await bucketFile.getSignedUrl({
            action: 'read',
            expires: '01-01-2050',
          });
          resizedImages.push(result[0] ? result[0] : '');
        }

[NickFoden]

In the extension configuration steps within the firebase console, there needs to be an option to enable the access token for the created thumbnails or could/should even be defaulted to a valid access token similar to behavior of the regular file upload to storage.

This is crucial for being able to use this extension. Was searching on how to use the created thumbnails and have only hit dead ends. I am not sure which use case is currently being solved with this extension if the generated thumbnails are not available for use? Seems we have to go another direction for thumbnail generation for now. If anyone has any ideas how to access the thumbnails please ping me. Anyhow looking forward to future version of this image resize extension. Txs all.

[lsps9150414]

@NickFoden Have been stuck with this as well. My workflow is:
Client upload to storage => resize extension => onStorageFinalize => cloud function to blur image & upload to storage again

So in the end, I have:

• the original uploaded image
• the resized images
• the blurred images

I cannot find a solution to generate/get the downloadable URLs (containing the tokens) of the resized & blurred images in the context of my cloud function to store to my Firestore DB so I ended up with only storing the file path (the name prop. from the data object) in the DB and doing getDownloadURL on the client-side with the firebase client SDK, which is not ideal tho but is the only way I have found so far.

[DhavalW]

+1 & I don't think this is a token access issue.

In my workflow, I'm serving some images & assets from a path fully open to public. ie Access rules are set to :

match /public/{allPaths=**}{
    	allow read, write;
    }

For every asset I manually construct the public url for this path, and purposely do not include any access tokens. So far all images were served just fine. However images generated by this extension are not served.

Unfortunately that's a deal killer for me, so i will have uninstall this extension & write my own image resizer. dread

[NickFoden]

If you go find the new asset in your storage you can see the issue. Say you upload random.png go view in the web console and find it in storage. Expand file location and see an Access token

Now do the same thing for the generated thumbnail say random_200x200.png. There is no access token set, and so you will get a 403 trying to use it in your application unless you go enable it's access token manually. But no way I can do this for every single crop being uploaded. This was my experience a few weeks back trying this out. Will need to have the access token set up when the cropped image is created, same as a normal image uploaded gets a working access token.

[DhavalW]

@NickFoden Yep. tried that just afterwards and you're right - it works once the token is enabled. & since its manual, doing so at scale is simply not an option.

But why does it occur even when auth requirements are disabled in rules ? that doesn't make sense. All other images on that path get served just fine without a token.

Also shouldn't this issue be marked as a bug ?

[Ehesp]

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

[dfdgsdfg]

signedUrl error log with non exist token status

@anthowm same case here.

I create signedUrl with adminStorage.bucket(bucketName).file(filePath).getSignedUrl(options), but it does not work.

<Error>
<Code>SignatureDoesNotMatch</Code>
<Message>
The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.
</Message>
<StringToSign>
GET 1895632947 /project.appspot.com/users/NK8bDKYlaofgwkX6cxy14tqpsGa2/room_backgrounds/room_bg_1584592936559_Ib6R9sawuIQ_200x200.jpeg
</StringToSign>
</Error>

If I create access token on web ui after created signedUrl, it still does not work.

[QuentinSc]

Hello,

No news ? :)

[DhavalW]

+1 waiting for a fix

…

On Tue, 31 Mar 2020 at 20:26, QuentinSc ***@***.***> wrote: Hello, No news ? :) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#140 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADRLL6H4ITQNE6PTZQAASXTRKIADJANCNFSM4J5BQBPA> .

[K0EZ]

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

[devth]

I just installed this extension, and by default it looks like the resized images don't have tokens, so I can't see them in the Firebase Console. Is that expected?

[felix-lambert]

Yes same for me I don't have the public token url

[dackers86]

Hi @devth @felix-lambert

I'll reopen this issue for investigation.

[dackers86]

Hi @devth @felix-lambert.

I am currently unable to replicate a missing token, can you confirm which version of the extension you are using?

The latest version is currently storage-resize-images@0.1.22

[felix-lambert]

Hello thanks for your help. Yes I can confirm that the public token url is not available on the resized image in version 0.1.22. I only have the storage (gs://....png) but not the access token. The image with the original size has the access token but not the resized image.

[dackers86]

Can you confirm that the File location tab on the right does not contain a token in Firebase storage?

Apologies if I am looking in the incorrect location.

[felix-lambert]

I have a file location tab. It contains: gs://.../mint.png for example but I don't have an Access token tab on the right for the resized image.

[dackers86]

Hi @felix-lambert.

We have so far been unable to replicate this issue, if you are still experiencing an issues.

If you are still seeing this issue, would it be possible to generate screenshot of the screen where you missing a token, all other generated instances appear to display this token for all images.

[danaia]

After a successful upload to my Firebase Bucket, I used to get my downloadURL just fine. Now, when using the resize extension, a new token is generated and I do not have access to the public image via the downloadURL - I tried to create my own uuid4 in metadata and still not working...

[i14h]

@dackers86 lets reevaluate where we are on this

[dackers86]

Possibly related #998

[yamankatby]

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

[CalvinJamesHeath]

@yamankatby I have it set to false but the images are still public. I'm I missing something?

[jauntybrain]

Hi @CalvinJamesHeath! Could you please provide more information about this issue? Most importantly, what URL are you using to access the image?

[jauntybrain]

@CalvinJamesHeath the only way I was able to replicate this behavior is when the Cloud Storage read permission is set to true (see screenshot below). Could you please verify your bucket's rules include the read permission set to false?

[CalvinJamesHeath]

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