Signal-desktop: Sticker pack is not uploaded: cannot read property "encryptAttachment" of undefined

Created on 26 Apr 2020  路  5Comments  路  Source: signalapp/Signal-Desktop

Bug Description

When trying to create a new Sticker pack, as soon as i want to upload the pack the error "cannot read property 'encryptAttachment' of undefined" appears and no upload seems to happen.

Steps to Reproduce

  1. Open the sticker pack creator
  2. Add stickers from https://gitlab.com/betalars/helpful-recources/-/tree/master/Mental_health_stickerpack/stickers
  3. Assign emojis
  4. Set name, author and icon
  5. Press continue
  6. Press upload

Actual Result:

For a few seconds, a box appears on the right side of the cancel button saying: Error uploading stickers: cannot read property 'encryptAttachment' of undefined.
Repeating the process results in the same behavior.

Expected Result:

Stickers are uploaded.

Screenshots

Screenshot_20200426_194357

Platform Info

Signal Version: v1.34.0-beta.1

Operating System: Arch Linux

uname -a
Linux hostname 5.6.6-arch1-1 #1 SMP PREEMPT Tue, 21 Apr 2020 10:35:16 +0000 x86_64 GNU/Linux

lsb_release -a
LSB Version: 1.4
Distributor ID: Arch
Description: Arch Linux
Release: rolling
Codename: n/a

Linked Device Version:

Android 4.58.5

Link to Debug Log

https://debuglogs.org/4d57fec55b239765116f9d9a0dac9873b82f235e9b11c51728c07c4f2eba2144

Mobile device Log:
https://debuglogs.org/c29ccc3d39a58bd7c814c67e75c30205c958ee42254fc705bf926f349fcea8cf

Bug

Most helpful comment

Thanks for the bug report. We'll have a fix in the next beta release.

All 5 comments

Thanks for the bug report. We'll have a fix in the next beta release.

I had the same issue on v1.34.0-beta.1. On v1.34.0-beta.3 no such error occurs.

@williamvds How did you install Signal Desktop?

@williamvds How did you install Signal Desktop?

Via the Arch User Repository package which pulls builds directly from https://updates.signal.org. I suspect @moonlies did the same.

I just tested the sticker creation process on v1.34.2 on Ubuntu 18.04. This appears to be due to the packaging process used in the creation of the Arch package. I'm going to close this.

Was this page helpful?
0 / 5 - 0 ratings