-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
App crashes when decoding image sent via telegram #9
Comments
Sorry i meant "decrypting" in the title. |
thanks for reporting this crash, and pointing to where I can handle the exception. the rest of the team can answer about where crash reports go, but this is the best place for me to see your issues. I haven't tested whether Telegram sends the original image or if it gets downsampled/requantized in chat; thanks for putting it on my radar. |
I tested to decrypt the message from the sent image on the senderphone, but pixelknot told me there is no message inside the image, so I think Telegram compresses the image in a way the message gets lost. |
that is probably the case. I also just pushed an F.A.Q. section to address that, and it should show up in the next build. |
Perhaps you could try using something like ToGoZip to 'zip' the image, then send the resulting file via Telegram. |
How do i see the message that i locked.? |
Share the image that contains your message with Pixelknot by choosing it in Android's share dialogue. |
I've just tried it and can confirm the issue. However, there's an easy work-around that worked for me: In Telegram, simply choose to send your image as an uncompressed file instead of a compressed in-chat image.
|
We could support zipping the image in PixelKnot. We do this already for ProofMode. Maybe we will add as an option. |
Hi
Pixelknot crashes when trying to decrypt message from photo sent from a nexus 5 to a Huawei Ascent P7 via telegrams private chat.
Reason is an ArrayIndexOutOfBoundsException thrown by method DECODE in info.guardianproject.f5android.plugins.f5.ortega.HuffmanDecode (line 411).
Also, whats the proper way to send you guys Crashreports? Will you get them when I click "send report" in the popup that opens when an app crashes?
The text was updated successfully, but these errors were encountered: