Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Render/Send File Attachments via WhatsApp #2108

Closed
lizhutter opened this issue Jul 5, 2021 · 3 comments · Fixed by #2574
Closed

Render/Send File Attachments via WhatsApp #2108

lizhutter opened this issue Jul 5, 2021 · 3 comments · Fixed by #2574
Assignees
Labels

Comments

@lizhutter
Copy link
Contributor

lizhutter commented Jul 5, 2021

We need to be able to render image, video, text, and PDF files via WhatsApp. We should also be able to send them via WhatsApp through in the UI.

  • Image, video, text and PDF files up to 5mb in size
  • Can send media messages up to 16mb in size (including the image, video, text, or PDF file)
  • To send a media message with WhatsApp, we need to include the MediaUrl parameter in your HTTP POST requests

Media content is currently only supported in Session Messages. Messaging sessions are created when a user responds to a template message you send them, or starts a conversation by messaging your number on WhatsApp. These sessions stay active for 24 hours after the last message they send you. If the WhatsApp session with a user expires, you must wait for an inbound message to create a new session before you can send them a media message.

Through Twilio:WhatsApp, the following file types are possible:

  • Images -- JPG, JPEG, PNG
  • Audio -- MP3, OGG, AMR
  • Documents -- PDF
  • Video -- MP4 (with H.264 video codec and AAC audio)

Design Note

With video files, we should not have a video player in the beginning. Instead, we should allow users to download the file and then watch it.

Design Note

122225089-bf91b600-ce82-11eb-9a1b-012bfacda270

We can use the same order of the icons within the input bar that we already have (emojis, templates, attachments).

Design Note

Please use the paperclip icon from this website:
Screenshot 2021-06-16 at 08 56 56

@chrismatix
Copy link
Contributor

Requires #2168 to be done first

@chrismatix
Copy link
Contributor

When implementing this, it's important to note that upfront it's only supported for Canada & US when using SMS https://support.twilio.com/hc/en-us/articles/223179808-Sending-and-receiving-MMS-messages

@lizhutter
Copy link
Contributor Author

Hey good eye @chrismatix, I previously spoke with Twilio about MMS and this article/reasoning is the exact reason why I hadn't made a ticket for rendering/sending file attachments through SMS/MMS, and rather only via WhatsApp

@lizhutter lizhutter added this to To do in Engineering WIP via automation Sep 6, 2021
@AudreyKj AudreyKj self-assigned this Nov 5, 2021
@AudreyKj AudreyKj moved this from To do to In progress in Engineering WIP Nov 5, 2021
@AudreyKj AudreyKj assigned AudreyKj and unassigned AudreyKj Nov 5, 2021
@AudreyKj AudreyKj moved this from In progress to Done in Engineering WIP Nov 10, 2021
AudreyKj added a commit that referenced this issue Nov 15, 2021
* whatsapp attachments wip

* rendering whatsapp wip

* whatsapp rendering wip

* inputselector wip

* fix inputselector

* decoded twilio message

* fixed whatsapp rendering and improved inputselector

* abstracted attachment type list

* improve wa render and inputselector

* fix logs

* added google sending attachments

* wa sending attachment

* logs cleanup

* inputselector animation and fixed emoji bug

* wa attachments fix wip

* oreview attachments

* finalized attachments whatsapp, messagepreview, inputselector

* fix outbound wa

* untracked file

* linting

* untracked

* fix mapper + linting

* lint

* fixed inputselector

* fixed disabled for file input

* fix messageList grow

* added blue border messagelist
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

3 participants