https://bugs.kde.org/show_bug.cgi?id=401677
--- Comment #86 from Stanislav <s.selets...@gmail.com> --- (In reply to Simon Redman from comment #84) > > Sorry to hear that you're still having this problem. > > If you're not seeing *any* exceptions when using the build from Binary > Factory, then I don't know what's going on.. Pretty much the code has to > return something or throw an exception. It's possible it's returning empty, > but that would be strange. > > When did you download the nightly build? I actually touched this codepath > over the weekened. (In a fairly significant way which I would expect to be > supported by most/all devices) Thank you for the swift reply, Simon! I tested build #709 yesterday, and I also tried build #710 today. What I do is to install APK, allow SMS (and other permissions), run `adb logcat --pid=$(adb shell pidof -s org.kde.kdeconnect_tp)` and then run `kdeconnect-sms`. It stays in the loading state forever, and I do not see *any* messages that appear right after running `kdeconnect-sms`. Note that when I was trying Play's version of the app, I saw the SQL error from the linked ticket. Other functions of `kdeconnect` work without a problem. I tried to test it with a different device (with Play's version of the app though), and `kdeconnect-sms` was able to display messages instantly, so I suppose it's a problem with the device itself. Could you create a debug build with additional debug/trace level logging enabled for the relevant code path so that I can provide `adb logcat` output? -- You are receiving this mail because: You are watching all bug changes.
