With Mastodon and Fedilab 3.5.0, it does not seem that planned boosts are actually boosted.
Is there something specific that should be done for this feature to work?
Programmed/planned boosts are not actually boosted #383
Have you tried without battery optimization for Fedilab?
I removed the battery optimization, will try again later on, but shouldn't the missed boosts at least be boosted (potentially late) when I reopen the app?
Because it just seemed that missed boosts are just ignored at the moment.
There are still some posts that fail to be boosted from time to time.
It is hard to know whether it is due to the app stopping (despite my disabling of the battery optimization), because another account is in the foreground, or because of a temporary network failure.
What seems sure is that, once the time has been missed, the app never tries to boost the post again. I think this should be considered a bug and the app should retry the boost whenever it comes back online or network is back.
I have the same problem (Fedilab 3.7; Android 13 Samsung).
There are still some posts that fail to be boosted from time to time.
It is hard to know whether it is due to the app stopping (despite my disabling of the battery optimization), because another account is in the foreground, or because of a temporary network failure.
It also fails if one has already boosted a post. This might be obvious, but it wasn't for me. It also doesn't warn, if a post has already beeen boosted when selecting the planned boost option. It could be another reason to the ones mentioned above.
I think it would be good, if there were an option to "unboost, boost again". It would have to wait, since it sometimes needs a moment, before one can boost again (maybe especially because of the current load in the Fediverse). The webclient warns that a toot is already boosted when quickly unchecking and rechecking the boost icon.
A warning if it fails utimately would be good. Also for the planned toots (which fail a lot for mee too, but I try and look some more option to disable battery optimization).
Hi, I found this issue multiple times and focus it on #933 (it is a part of this issue). Your input is not lost since it's referenced. Please follow there for updates. Thank you!
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?