Latest release sent old timed messages

[PowerUser64]

The timed messages feature was broken for me for a while, but it was fixed in the latest release. I had a few old timed messages that got sent as a result. No harm done, just a few really confused people 😂

[Inhishonor]

@PowerUser64 Can you test to see if this happens again next release? Sorry, if my reply is to late for 4.1.1. The scheduled messaging functionality received a huge rework in the latest release so that could be the cause.

[PowerUser64]

I'm guessing the rework is what caused it. I'm still on v4.1.0 (I get updates from f-droid so they're slightly delayed). I could test something if you'd like. Although, I don't think I can recreate the conditions of before too easily. I could reinstall an older version if you'd like. (Wouldn't be much trouble.)

Before the update, the timed messages feature didn't work 90% of the time for me, so I would schedule a message and it usually wouldn't send. Sometimes it would work though, so I still used it for some non-critical things. When it didn't work I would just leave the scheduled message alone in the purgatory of the "scheduled" bin that it appeared in (even though I thought it would never send). What I think happened is the rework unfroze those old messages that were stuck in purgatory, so they got sent immediately.

Right now, message scheduling seems to work fine, so I don't think I can reproduce these conditions on this version alone.

It might be good to introduce some sort of internal time window (maybe an hour to a day, or even a week) that the message will try to send in, starting from its scheduled time. Then if it tries to send outside that window, it will prompt the user to let them know the scheduled message couldn't be sent on time (maybe the device was powered off), and ask if they want to send, edit, or delete it. This way things don't get lost in the bin or sent at a very wrong time.

[Inhishonor]

Right now, message scheduling seems to work fine, so I don't think I can reproduce these conditions on this version alone.

That is fine, the only thing I can think of at this moment would be to schedule some messages before you update the app and if they don't send I think we are out of the woods.

It might be good to introduce some sort of internal time window (maybe an hour to a day, or even a week) that the message will try to send in, starting from its scheduled time. Then if it tries to send outside that window, it will prompt the user to let them know the scheduled message couldn't be sent on time (maybe the device was powered off), and ask if they want to send, edit, or delete it. This way things don't get lost in the bin or sent at a very wrong time.

I really like this idea, this should probably be implemented. The only potential problem I could see would be battery life. 🤔