Qksms: Archive state reset when not default SMS app

[nosoop]

DESCRIPTION

Archived messages return to the inbox if QKSMS is not the default application.

STEPS

1. Install QKSMS.
2. Launch application, skip making QKSMS the default SMS application. Wait until database is optimized (I had to restart the application a few times for it to complete).
3. Archive some conversations.
4. Exit (via back button) and reopen the application, skip the prompt making QKSMS the default again.

Alternate steps where QKSMS is already used as the default:

1. Archive some conversations, if not already.
2. Install / set another application as the default for SMS and exit.
3. Reopen QKSMS, skip making it the default application.

EXPECTED

Previously archived conversations should remain archived, but instead they are all visible in the inbox list and the archived list remains empty.

Tested on current latest F-Droid build, 3.1.1.

Not ready to make it my daily driver for SMS just yet, but glad to hear it's back in development!

[moezbhatti]

Hmm, I'm not able to reproduce this on my own device on 3.1.3. I'll do some more testing and see what I find

[nosoop]

Testing with a Nextbit Robin on Android 7.1.1 with a few thousand messages on some contacts. Also occurs for me if QKSMS is swiped away / force closed in settings, but not when pushed to background.

Checked against F-Droid version 3.1.3 and Google Play version 3.1.3; occurs on both for me. Wiped application data between a few runs to be completely sure, too.

It also unarchived messages for me with the following steps:

1. Start the application without QKSMS as the default SMS application.
2. Archive a few messages.
3. While in the inbox or archived views, open up the settings.
4. Use the "Default SMS app" setting to set QKSMS as the default.
5. Return to the previous message list. All messages will be in the inbox again.

[moezbhatti]

I've changed some things with how the message syncing is done after the app is set as the default SMS app, in version 3.2. I'll be releasing it in the next couple days - once it's out perhaps you can try it out and let me know if does anything for you with respect to this issue

[nosoop]

F-Droid hasn't picked up the new version yet, but it does seem to be fixed in 3.2.

Thanks!