kdeconnectd crashed with SIGSEGV in KIO::TransferJob::sendAsyncData()

[Elroy]

The app crashed while trying to send files from phone to pc

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: kdeconnect 1.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Mar 12 23:04:43 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
InstallationDate: Installed on 2018-03-12 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180312)
ProcCmdline: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fdc7defee12 <_ZN3KIO11TransferJob13sendAsyncDataERK10QByteArray+50>: mov (%rdi),%rax
 PC (0x7fdc7defee12) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdeconnect
StacktraceTop:
 KIO::TransferJob::sendAsyncData(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
 QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
Title: kdeconnectd crashed with SIGSEGV in KIO::TransferJob::sendAsyncData()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1746906, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.