Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No image preview for OMEMO encrypted files
See original GitHub issueUsing HEAD (01efb02f9e55aaaf1d27a3b77a8bc7f96e1cde88)
Neither sent, nor received are shown when using show_images_inline
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
View/download omemo encrypted image/file in history
All downloaded and decrypted pictures are in a folder on your harddrive. no there is no technical reason why it isnt shown in...
Read more >OMEMO Media sharing - XMPP
The resulting aesgcm URL is encrypted as an OMEMO message and send to the recipient(s). The sending entity MAY also generate a thumbnail...
Read more >aTalk (Jabber / XMPP) - Apps on Google Play
aTalk - xmpp client for android rich in features: * Instant messaging in plain text and End-to-End encryption with OMEMO or OTR
Read more >Why are there no thumbnails and previews for encrypted ...
Currently, the web app does support previewing images, PDF documents, audio and video files directly within browser as the encrypted files can be...
Read more >Picking and setting up modern XMPP clients
So let's activate OMEMO encryption by pressing the padlock in the top ... it and fail to decrypt the OMEMO encoded image, because...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jcbrand Thanks, fixed
@licaon-kter Please check whether the latest commit fixes this issue. Thanks.