Bug 371024

Summary:	SMS Reply button doesnt appear and text truncated
Product:	[Applications] kdeconnect	Reporter:	John lanser <john.lanser>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	piotr.mierzwinski
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Screenshot of notification window

Description John lanser 2016-10-17 20:29:46 UTC

Opensuse Leap 42.1.20160217
Connect 1.0.1-12.6
Android 6.01 Android connect app 1.4.4
Samsung Galaxy S5

Reply button doesnt show when a message is received and cannot read all the message happens every time I get a sms

Reproducible: Always

Steps to Reproduce:
1. Received Text
2.
3.

Actual Results:  
as per screenshot

Expected Results:  
No reply button and only part of text visible licking on t doesnt expand

Comment 1 John lanser 2016-10-17 20:30:39 UTC

Created attachment 101606 [details]
Screenshot of notification window

Comment 2 Piotr Mierzwinski 2017-01-18 20:36:41 UTC

About part message. I noticed that it happens when sender uses emoticons. Otherwise I can see whole message.

Comment 3 John lanser 2017-01-18 22:50:01 UTC

Now using 
Opensuse Leap 42.2
Connect 1.0.1-12.8
Android 6.01 Android connect app 1.5

no change still no reply button or message expansion

Comment 4 Piotr Mierzwinski 2017-01-18 23:02:01 UTC

I use kdeconnect 1.0.3 (Plasma) and I can see reply button.
The only one issue is that when you do not hit the button you will lose possibility to reply (in kdeconnect) :-(. Unfortunately history is missing.
And as I said before truncated message happens when received SMS contains smileys. I made two tests. First for SMS with smileys and second without.

Used software:
kdeconnect 1.0.3 (Plasma)
Qt-5.7.1, KF-5.30, Plasma-5.8.5
Up-to-dated Antergos.

kde connect 1.5 (Android)
Android 5.1.1

Comment 5 Albert Vaca Cintora 2017-01-19 16:03:40 UTC


*** This bug has been marked as a duplicate of bug 369179 ***