GCS file adding problem

Queries and Resources
1

When I click the preview of the resource for uploading the image to GCS, there is an error message "Cannot read properties of null (reading 'contentType')". The screenshot is as follows:

gcs_preview
gcs_preview1928×646 58.7 KB

And when I click run of the resource for uploading the image to GCS, there is an error message "Upload2Firestrage: Cannot use Access level with a Uniform Access Level bucket. Please remove Access level from your upload query."

Does anyone encounter this problem before?

2

Hi there @cekhwang !

I'll gladly assist you with this!

Taking a look at the screenshot, I was just curious about what you were indexing in firebase.filepicker.files, sometimes you're using a string 0 and then you're using the integer 0. Should they be consistent for your file setup? Or is that intentional?

For the second error, this error occurs from trying to include an Access Level on a file upload to a bucket that uses Uniform Access Control. Does leaving the file blank lead to a successful upload?

3

Hi there @DanBlonc !

I got the same problem and when I upload a "blank" file it leads to a successfull upload, but when I place any kind of info in "Upload data" it says "Cannot read properties of null (reading 'contentType')"

1 Like
4

I'm also having this exact same issue.

5

Hi all,

Hm, would using custom values to set the content type work here?

6

I am experiencing the same issue, even when manually specifying the content type.

There are many community support pages referencing this problem, but I've yet to uncover a solution.

image
image1428×1612 211 KB

7

Update: I have found that this error surfaces only when using the Preview button. If you click the Run button, it succeeds.

So this is clearly a bug.

8

Hey folks!

Certainly odd behavior here. Some more questions for extra context as it doesn't look like we've been able to reproduce this particular instance yet:

  1. Are you seeing the files upload properly when clicking "Run"? What about "Preview" (even though the query fails)?
  2. Is this happening consistently across files of different types?
  3. Is there any additional messaging in the network tab of your browser's dev tools?
  4. Finally, is this new behavior? And if so when did it start?

To expand on that last question - I know this thread is old but I just want to pull things apart a bit in case we're seeing the same symptom show up for different reasons.