search

newhinton / Round-Sync

An android cloud file manager, powered by rclone. Visit https://roundsync.com for more information!
https://roundsync.com
GNU General Public License v3.0
1.31k stars 51 forks source link

App fails to launch after adding a trigger #244

Closed kctdfh closed 7 months ago

kctdfh commented 7 months ago

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

Version 2.2.2

What is your Android version, phone model and manufacturer?

Pixel 8 Pro 14 (AP1A.240405.002)

Which steps are required to reproduce this issue?

I've been using the app without issue for at least a year. Decided to use the "trigger" function for the first time and now the app doesn't launch anymore.

I don't exactly remember the nature of the trigger but I think it was: for my "rclone copy" task on the DCIM directory, to run daily, at 4am, from local to B2 (which works on Termux and desktop - and has worked in Round Sync before as well).

Tried deleting the cache but didn't help. Don't want to reset app data because I'd loose all of my tasks.

What is your configuration (rclone.conf)?

Not applicable in this instance since the bug doesn't seem to be rclone related

newhinton commented 7 months ago

Huh, i have never encountered that one.

From a quick glance, it might be due to a missing runtime-permission for scheduling alarms. I cant find the setting right now, but can you check if you granted that one?

kctdfh commented 7 months ago

Do you mean app permissions? In that case, in App Info I can only grant "Notifications", which is granted.

But there's a "more settings in the app" button in the App Info screen that strangely enough opens the app successfully to its Settings page.

From there, I've made sure it's pretty permissive overall but there's one toggle that seems to be disabled, and that is the background operation toggle. Not sure if it's related but I can't seem to be able to toggle that ON.

On Mon, Apr 15, 2024, 2:39 PM Felix Nüsse @.***> wrote:

Huh, i have never encountered that one.

From a quick glance, it might be due to a missing runtime-permission for scheduling alarms. I cant find the setting right now, but can you check if you granted that one?

— Reply to this email directly, view it on GitHub https://github.com/newhinton/Round-Sync/issues/244#issuecomment-2057570066, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4JGDZC45JBXYBTVEG7VDDY5QNF3AVCNFSM6AAAAABGH3VQS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJXGU3TAMBWGY . You are receiving this because you authored the thread.Message ID: @.***>

newhinton commented 7 months ago

Okay, first thing you shoud do then is create a backup of your config :D

You should also be able to open the trigger page, and disable any triggers for now. I'll take a deeper look later.

kctdfh commented 7 months ago

Haha yeah no worries on that front - my config is the same on multiple devices.

I actually wasn't able to go to another page. Pressing "Back" would just take me back to App Info because that's where I came from.

I deleted all the app data and obviously that fixed the issue. Let me know if you want me to do it again to help you debug this!

On Mon, Apr 15, 2024, 3:09 PM Felix Nüsse @.***> wrote:

Okay, first thing you shoud do then is create a backup of your config :D

You should also be able to open the trigger page, and disable any triggers for now. I'll take a deeper look later.

— Reply to this email directly, view it on GitHub https://github.com/newhinton/Round-Sync/issues/244#issuecomment-2057618205, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4JGD5RIT2TRJBCYYFOKDTY5QQVRAVCNFSM6AAAAABGH3VQS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJXGYYTQMRQGU . You are receiving this because you authored the thread.Message ID: @.***>

sasjafor commented 7 months ago

I'm having the same issue also on a Pixel 8 Pro, but version 2.2.3-terrapin

Itchyfantastico commented 7 months ago

I'm having the same issue also on a Pixel 8 Pro, but version 2.2.3-terrapin

Same here with a Samsung Galaxy S24

newhinton commented 7 months ago

@sasjafor @Itchyfantastico Which android versions are you running? 13/14?

newhinton commented 7 months ago

It would be very helpful if someone could post a logcat of the crash.

newhinton commented 7 months ago

From what i found, this is an issue specific to android 13 and later with roundsync 2.2.3 and eariler. I am planning on releasing 2.5.1 today, that should fix the issue.

sasjafor commented 7 months ago

I'm on Android 14. I can try to get a logcat later today.

Itchyfantastico commented 7 months ago

@sasjafor @Itchyfantastico Which android versions are you running? 13/14?

I'm on Android 14 as well

newhinton commented 7 months ago

Please try the latest release, it should work again!

sasjafor commented 7 months ago

It's looking good! It's not crashing anymore. I will wait until the timer I setup has run once to fully confirm.