Bug 446476

Summary: notifications from android do not have correct app name after latest android app update
Product: [Applications] kdeconnect Reporter: johnathan <testing1237a-c>
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolas.fella
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: notification

Description johnathan 2021-12-04 14:32:23 UTC
Created attachment 144212 [details]
notification

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
check attached screenshot. it shows the name of the app as "im.vector.app" when it should say element. this happened right after i updated android app from f-droid. 
1.18.0 is my android kde connect version. 


STEPS TO REPRODUCE
1. receive notification on phone
2. check desktop notification sync
3. name of app is internal name not user name of the app.

OBSERVED RESULT

im.vector.app in name of app which received the notification
EXPECTED RESULT
element in name of app which received the notification

this started happening right after android update but i could not open spectacle quickly to take  a screenshot or photo. had an idea to use element troubleshoot notification setting to test this. 

and yes. this happens with all android notifications. 
SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4400
Comment 1 Nicolas Fella 2021-12-04 14:57:35 UTC

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