
Unlawful Cactus
@Tom I'm still not getting notified when S3Drive fails a sync job. I have to open the app AND check the Sync screen to find out. Just found out my data didn't get backed up for 3 days
️
All notifications for S3Drive are enabled in Android settings. The backgroundServiceError channel remains unused, the backgroundService channel only shows the regular background sync messages.
Is this expected to work this poorly or is something wrong on my end? Not talking about the sync job failing sometimes—which I've previously understood is hard to get a grip on—but about the lack of notifications. I know, it's embarrassing that we still didn't address this issue. The good news is that there will be improvements included in a next release. There will be notifications for sync and media backup, including their respective background modes.
Each job will start with start notification, which will get deleted once job is successfull. If job fails, it will end up with a failure message with slightly higher priority and importance. If job fails in the middle (e.g. freeze or some uncaught exception) the initial start notification will persist indicating potential failure.
Each sync job in particular will use own notification ID and text message will include e.g. "Starting move from /DCIM to s3drive_josh:", so e.g. success of job A won't remove notification indicating failure of job A.
This is our initial approach / simplification of the whole notification system that we can apply to all platforms, including Android. This is also starting point for further improvements, improved notification details etc.