lone-faerie

I got it to work by going into the Syncthing GUI and disabling TLS, and then setting the plugin to use http

See https://github.com/slavabarkov/tidy/issues/28#issuecomment-2461169323 I fixed this by deleting any pictures in the root directory (/storage/emulated/0)

See https://github.com/slavabarkov/tidy/issues/28#issuecomment-2461169323 I fixed this by deleting any pictures in the root directory (/storage/emulated/0)

The reason for each push provider having its own class is to support multiple protocols, as well as helping to separate things between minimal and full. Like @TimoPtr said, it's...

Ok, I get what you're saying. I was planning on initially just using the default UnifiedPush distributor with ` UnifiedPush.tryUseCurrentOrDefaultDistributor(context)` just to get things working at first. But there's a...

> That could be an option. What would you return for that function in the FCM push provider? For the FCM provider, I'd either return `null` or "FCM" (or "Firebase")....

Yeah, sorry I've been moving so haven't had any time to work on this. I'm finally settled in so I'll start up on this again soon

The push provider should only change during onboarding or if the user uninstalls the distributor app. A generic interface does feel like the more proper approach though, perhaps something like...

I was having this issue too and this was the logcat message I was getting. I managed to work around it by deleting any pictures from my storage root directory...