App crash on scheduled trigger enable

[leoj3n]

What version of Round Sync are you using (About -> App version)?

2.2.2 as well as 2.2.3-terrapin

What is your Android version, phone model and manufacturer?

Google Pixel 8 Pro

Which steps are required to reproduce this issue?

1. Create a trigger that is scheduled (not interval)
2. Uncheck enabled so it doesn't crash right away
3. Save
4. Enable the trigger
5. Round Sync crashes
6. Subsequent launches immediately crash
7. Not seeing any error logs from internal storage
8. Have to clear storage for the app
9. Now the app will launch and work as expected until attempting creating an enabled scheduled trigger again.

rclone.conf:

[5d44cd8d-397c-4107-b79b-17f2b6a07dr9]
type = alias
remote = /storage/emulated/0

[leoj3n-gdrive]
type = drive
client_secret =
client_id =
token = {"access_token":"","token_type":"Bearer","refresh_token":"","expiry":""}
team_drive = 

[leoj3n-gdrive-crypt-daily]
type = crypt
rclone_remote_name = leoj3n-gdrive-crypt-daily
password =
remote =

[leoj3n-gdrive-crypt-rare]
type = crypt
password =
remote =

rcx.json:

{"tasks":[{"id":1,"name":"Backup Backups","remoteId":"leoj3n-gdrive-crypt-rare","remotePath":"\/Pixel8ProBackup","remoteType":13,"localPath":"\/storage\/emulated\/0\/Backups","syncDirection":1,"md5sum":false,"wifionly":false}],"trigger":[{"id":1,"time":15,"title":"TriggerBackup","weekdays":127,"target":1,"enabled":true},{"id":2,"time":0,"title":"TrggerAppCrash","weekdays":127,"target":1,"enabled":false}]}

rcx.prefs:

{"showThumbnails":false,"isWifiOnly":false,"allowWhileIdle":false,"useProxy":false,"proxyProtocol":"http","proxyHost":"localhost","proxyPort":8080,"safEnabled":false,"refreshLaEnabled":true,"vcpEnabled":true,"vcpDeclareLocal":true,"vcpGrantAll":false,"isDarkTheme":0,"isWrapFilenames":true,"appUpdates":true,"betaUpdates":false,"useLogs":true,"crashReports":false}

[leoj3n]

Maybe an issue in here Services/TriggerService.java?

[leoj3n]

Looks like the issue is resolved in RoundSync - v2.4.3-beta

[newhinton]

Closing because it is already fixed