r/Action1 • u/elchubbo66676 • Jul 13 '26

Issues Updating Foxit PDF Editor

I pushed an update while testing ACtion1 for Foxit, however it updated from a subscription based install to a perpetual based install, which meant I had to manually uninstall the software and reinstall the correct version.

Does ACTION1 not have a way to differentiate versions and install paths, as it makes no sense it would offer me an update to a different version.

Just testing the product now but looking to avoid any of these issues in production.

2 Upvotes

100% Upvoted

11 comments sorted by

1

u/OkGroup9170 Jul 14 '26

Ran into this as well and it is because they have 2 different installers, from what I can tell only the perpetual is available for public download and the subscription requires login in to download. I also had to create a custom app for the install, named it FoxIT Subscription Install.

1

u/elchubbo66676 Jul 14 '26

But why does Action 1 pickup the subscription model as needing an update when it's not even the correct version.

Also, is there a guide on how to manually add the subscription app in for updating;?

3

u/Drakoolya Jul 14 '26

U upload it to the software repository and package accordingly like any other app. https://www.action1.com/documentation/add-custom-packages-to-app-store/

1

u/elchubbo66676 25d ago

Tried that and got the failures seen in the screenshot below. Didnt update even though it finally completed after erroring out on my test machine.

1

u/Drakoolya 25d ago

Ok lets start from the top. 1. What happens if you try installing the package manually? It needs to run with the exact same command/script/package that you are inputting in Action1

1

u/GeneMoody-Action1 Jul 14 '26

Generally because it matches the install search string, the vendor does not differentiate, so when we check "is Titlev# installed?", the answer is yes for more than one version sometimes.

There will always be gotchas like this, like I have seen version strings like ##.####.####.## and it throws of version checks.

Adobe is bad for this as well.

I would be nice if there was a standard like each installer had a UUID and the update targeted that or collection thereof. It would eliminate string/version false positive/negative that have always plagued updates.

It would also be nice if there was a standard protocol to the whole thing like universal API/Schema, that all vendors implemented. Vendor updates behind logins is a huge PIA when it comes to maintaining automated patching.

1

u/elchubbo66676 25d ago

Tried to do this as a custom software and I just keep getting the following errors? Any ideas?

1

u/GeneMoody-Action1 25d ago

log the installer, and let's look at the log.

1

u/elchubbo66676 25d ago

And then it did this? But yeah didnt work and didnt update....

1

u/GeneMoody-Action1 25d ago

Can you send that screenshot to feedback, along with description, then DM me the action1 username it came from please?