Only happens if the image is send trough Whatsapp.
Web:
URL https://s3. ....
Everything fine.
Whatsapp:
URL https://paineltype. ...
"Not authenticated"
That's right, image from WA are private by default
that's a current limitation
I need to think of a solution
If I can help you with anything, please let me know.
It could be helpful if you share why things are like this, so we can think together.
And I'm open to any possible workaround to solve this, even temporarily, just so I can move forward.
Do you suggest any workaround that I could use until we have an official solution?
There are just no workaround for that... If possible, deploy the web chat for now. 🙏
In order to read the image stored on WhatsApp we need to be authenticated.
So I'm thinking of an additionnal option in the File upload block "Public URL" or something. And instead of parsing the URL that authenticates etc... we would automatically download the file from WhatsApp server and store it into the S3 storage for public access
we would automatically download the file from WhatsApp server and store it into the S3 storage for public access
That sounds ideal. However, since we are currently utilizing only the Text Block, I believe the corresponding option should be integrated into the WhatsApp integration rather than the File Upload block.
Alternatively, we might consider omitting the need for an option altogether and simply implementing this automatically.
Every file sent to the bot could be seamlessly stored in its S3 storage, regardless of its source.
That'd be sad to store files in 2 different storages WhatsApp + S3
Not as sad as not being able to use the image. 😆
But I got your point.
It will make sense to add the option to set the uploaded file private or public in the block settings.
Will work on that fairly soon 🙏
Thank you! 🙏
In the meantime, I'll try to find a workaround so I don't have to put the project on hold again.
I'll take a look in a few minutes
@Baptiste I saw you added the visibility to the FileUpload.
Can I use this somehow to solve my problem, where what I'm using is a Text Input (cause I don't know if the user will send a text or a file)?
set to Public and you should be good to go
Where?
I'm not using the FileUpload block.
I was kinda of expecting something here:
In the previous version, when I sent a FileUpload through WhatsApp and collected it with the TextBlock, I used to receive a private URL to the image, as show on the print screen. (I never utilized the FileUploadBlock for this)
In the current version, the same flow now returns an "invalid message" error.
This puts me in a worse situation than before. 😆
Yes you should use the File Upload block
With the Public visibility on
Ok, but....
If I use FileUpload block, user can't send text messages. Right?
So you need an input where the user can either send a text message or a file?
Can't you just know if you need a file or text before hand?
I had one. Text input.
it used to work for both (except by the fact that the URL was private).
Look at my old print:
Yes but it should not work
If you collect a text input, you shouldn't allow collecting an image
that would not make sense
On your flow, it looks like you are clearly asking for an image
Why don't you add a File input block?
To my flow to work the user is supposed to be able send text and/or image.
Ok then that will be another feature to implement
Ok, thank you for everything.
I'll have go back to the last version (where the Text Block used to accept file uploads) and try to bypass the private URL.
I'm running against the time.
