Help, Syncthing-Fork installation corrupted

GlytchMeister

So Syncthing-Fork made changes to their APK naming conventions which caused Obtanium to not see updates and then try to "update" to an older version.

The current release of Syncthing-Fork does not have information readily available concerning the new app ID issue.

I tried to export, uninstall, and reinstall (EDIT: because that's how this sort of issue has been solved in the past), but I figured I should keep user files because I thought that would delete the export I'd just made

And now I can't install any version of Syncthing-Fork because of some kind of conflict, even versions that should have the same app id

The only solution offered on Syncthing-Fork involves adb, and GrapheneOS strongly recommends against ever using adb.

I've tried going through my files and deleting anything belonging to Syncthing-Fork, but it's still not letting me install.

Can anyone help me figure out how to fix this? Or at least how to remove Syncthing-Fork, because after this experience and the answer I got from the Dev and the Syncthing-Fork community (blamed it on Obtanium, then on GrapheneOS, and then on me and told me to buy an iPhone), I think I'd rather find some other way of synchronizing files between my phone and my laptop.

warm-beer69

I had that same issue.
The signature of the new release changed so you need to uninstall the old version. Before uninstalling I used the app export feature and checked if it was created sucessfully (by default in the 'syncthing' folder in internal storage, that shouldnt be deleted after uninstall). In Obtanium I had to change the apk filter to 'syncthingandroid_release', and installed v1.30.0.1 (you may have to uninstall the old app in all profiles too because of the signature, not sure tho).
I tried to import my config with the new version, but it failed, because the default backup folder changed and the it requires a zip file rather than the all files in the directory. Just zip everything in the backup folder (without any extra directory, everything in the root of the zip file) and set the config archive path in settings accordingly.
You might have to change your paths because '~' represents '/storage/emulated/0/syncthing' rather than '/storage/emulated/0' in the new version.
Figuring that out did cost a few hours of my sleep, but it works now.

Murcielago

It was the same for me. I can no longer reproduce it exactly, so take it with a grain of salt: I had Syncthing-Fork v1.29.7.5 installed and Obtainium wanted to "update" me to an older version and displayed the error message you described in Obtainium. Since I didn't have time to set up Syncthing again, but couldn't do without it either (backups), I decided to live with Obtainium's error message until I had time to reconfigure Syncthing on my Pixel and computer.

After a couple oft days Obtainium simply updated me to
Syncthing-Fork v1.30.0.1 at some point and it is running now without any problems.

GlytchMeister

No, like... I already uninstalled. ALL VERSIONS do not install, now.

Obtanium says

Some Errors Occurred
Conflict [syncthing-android]

It's because I checkmarked "keep user data" when uninstalling because I thought that would delete the export I had just made

Apparently the proper way to update was to NOT keep user data, but there was nothing in the current version saying I had to do that.

I've tried deleting EVERYTHING that I can find in my files pertaining to Syncthing, even "hidden" files, but it still won't install.

Again, I already uninstalled.

The only solution offered by Syncthing-Fork is to use adb uninstall, and I really don't want to do that because GOS says to never use adb with GOS

Mystified3527

GlytchMeister
If you have it installed in some other profile you would need to delete that as well

GlytchMeister

I'm going yo have to wipe my whole phone, aren't I?

monozygote

GlytchMeister You probably already checked, but did you uninstall it from all the profiles, everywhere? It needs to go from everywhere. Easiest is to go to owner profile and select syncthing-fork and uninstall-from-all (or whatever that option is). Then yes, you can delete the user-data of syncthing-fork app and try to install again.

DeletedUser313

GlytchMeister You could just install it directly from fdroid or github as it has the APKs and uninstall it while removing user data. I had the same problem and I uninstalled from all profiles before it worked

Dumdum

GlytchMeister
Have you restarted your phone since uninstalling Syncthing? I faintly recall an issue where the OS will sometimes keep a trace of an uninstalled app until you refresh the device.

GlytchMeister

monozygote
It was only installed on one non-owner profile - I only have a few bare minimum apps installed on the owner profile, and I generally only use it to update the os - but I will check and report back once I finish replying here.

DeletedUser313
I'll give that a shot if I can't find some trace of it in the Owner's "uninstall for all" thing mentioned above and if rebooting doesn't work

Dumdum
I have not, I'll try that second

...

OK so it shows under settings/apps/see all apps/com.github.catfriend1.syncthingandroid, with a missing app icon and the only option I can tap in there is App Battery Usage, but I can't do anything in there. I can't uninstall, I can't force stop, I can't disable. It's a ghost app.

[Placeholder]

GlytchMeister

OK, rebooting didn't get rid of the trace I found. Gonna try installing through different means...

"App not installed as package conflicts with an existing package"

OK, so that's super cool, apparently syncthing-fork leaves behind a ghost app that can't be removed without compromising your OS's security through adb or root or whatever (are they the same thing?) if you uninstall while keeping user data, this is SUCH a well-written app lol, and the Dev made absolutely no effort to investigate and the community was up my rear end for "mindlessly pressing buttons"

Gawd I hate the internet sometimes

Awesome, I'm gonna have to use my distress code to wipe my phone and spend who knows how long setting it all up again practically from scratch

Either that or I just live with this busted piece of craptastic code on my phone

Uuuuuuuugh

de0u

GlytchMeister Just checking, have you tried installing exactly whichever version was installed when the deletion-while-keeping-data event occurred?

Which adb commands were suggested?

DeletedUser313

GlytchMeister What method did you use to install? It worked with F-Droid for me when that happened

GlytchMeister

de0u

I did try that. I can try it again just to make sure... Yep, doesn't work
Re: adb commands:

Enable Developer Options
Enable USB Debugging
Install adb
adb devices
allow connection on PC
adb uninstall com.github.catfriend1.syncthingandroid

That looks like they're asking me to not only do 1 thing GOS Devs say not to do or reccomend against for security, but 4 at least

de0u

GlytchMeister To my eyes that list is missing steps, resulting in reduced security. After the uninstall I think it would be important to:

In developer options, "Revoke USB debugging authorizations"
In developer options, turn off the floating "Use developer options" slider.

Then, depending on your OS, you would ideally hunt down and delete the RSA key from the PC, to avoid automatic reuse later in case somebody managed to snatch a copy in the interim.

All of that said, an expert might not agree with me.

GlytchMeister

de0u

Well that's just another reason for me not to trust Syncthing-Fork's programming and workarounds provided by the dev, jeeze.

The bits about undoing the settings changes are more or less a given, but I had no idea about the RSA key. I wonder how many folks are gonna follow the advice as provided and end up with less security.

GlytchMeister

DeletedUser313

Obtanium

wagg3r

I had a similar problem with an old version of syncthing-fork that I had uninstalled but left the app data intact and I wanted to get rid of it. I was advised to use the same adb commands and it worked fine for me, I'll check my notes when I have a chance and post what I used. I also searched to check the risks of adb to GrapheneOS before doing it and the advice I found was that the device should not have debugging left on, not that adb should not be used at all, although I'm happy to be corrected on this.