Can't send SMS on first conversation message send when Spacebar launched w/ app drawer icon

HW: PinePhone pmOS CE (3GB ram)

SW: (microSD) https://images.postmarketos.org/pinephone/pine64-pinephone-20200903-plasma-mobile-master-installer.img.xz

Problem: When attempting to send an SMS to a contact get a error message pop-up saying: "Could not find a sim account, can't open chat. Please check the log for details". This only happens when first starting a conversation by launching Spacebar via the app drawer icon. I don't get this when launching through Terminal. If a message already exists with that contact, it has no issues either.

How to replicate:

1. Get a phone w/ the pmOS Plasma Mobile
2. Add a contact
3. Send a SMS via Spacebar to said contact as a new conversation (if you don't want to reflash to get new conversation state you can run rm ~/.local/share/KDE/spacebar/messages.sqlite)

Other: Worth noting SMS works fine on Mobian w/ Phosh, so I don't think it's a sim issue w/ my provider

mentioned in issue #742 (closed)

By ... on 2020-09-04T19:58:26

added ui-plasma-mobile label

Strange, I've just tested this with @craftyguy and he received my SMS fine.

Are you sure you've unlocked your SIM card if you have a pincode set for it?

By Bart Ribbers on 2020-09-05T18:59:21

Don't have a pincode set for the SIM; reconfirmed w/ the now 9/5 image of Mobian that sending SMS works w/o issue and w/o tweaking anything out of the box. If someone tells me where to pull the logs referenced in the error message above I can do so in the hope it sheds more light on root cause w/ Spacebar

By ... on 2020-09-05T19:07:04

changed the description

By ... on 2020-09-05T23:26:38

changed title from Can't send SMS via Spacebar to Can't send SMS via Spacebar app drawer icon on first message send

By ... on 2020-09-05T23:30:26

changed title from Can't send SMS via Spacebar app drawer icon on first message send to Can't send SMS on first conversation message send when Spacebar launched w/ app drawer icon

By ... on 2020-09-05T23:32:38

Can you re-check with the git master if this is now fixed? !1677 (closed) includes the major rewrite from upstream.

By Bhushan Shah on 2020-11-03T15:44:02

This has been 3 years ago now and there has been no response to @bshah's request so I'm closing this. Please feel free to re-open if the problem still occurs.

By Bart Ribbers on 2023-12-05T10:14:42

closed