@Andreas_Hegenberg I have asked this question before, but unfortunately I can no longer find your answer.
Devonthink has changed something with the update to version 4, so that BTT no longer recognizes anything that was set up for version 3.
How can I fix this problem? Thanks.
Edit: Wouldn't it be easiest if you could simply select the new app in the context menu?
Similar to this
I don't know why, but Devonthink seems to change its bundle / app identifier when upgrading. In general these should always stay the same, but maybe they want to support running multiple versions at the same time.
The easiest way to resolve this is to use the "Alle Trigger fĂĽr die App kopieren" (Copy All Triggers For App) option in your Screenshot, then use the "Eine der aktiven Apps hinzufĂĽgen" Option to add the new version of DevonThink. Afterwards right-click the new version and choose "EinfĂĽgen" to paste all your Devon Think triggers. If you don't need DEVONthink 3 support anymore you can then delete that from BTT.
This is sometimes also the case with Parallels Desktop apps after an update. For example, in Visual Studio.
I think I could add a "Move To New App Version" option to the context menu that allows choosing a new app or CAG (equivalent to the + button to add a new app)
Ah, exactly. That was the solution. Thank you.
That might make it even easier.
Interestingly, CAGs are not a problem. At least not with Devonthink. There, I can simply adjust “app name contains”.
Added in 5.726 (uploading now):
Your CAG probably just checks for the app name "DEVONthink" and not "DEVONthink 3", but for exact matching without a CAG the app name is not enough - which is why that matching generally relies on the app bundle identifier (which for most apps stays the same for all time).
What you added in v 5.726 is very user-friendly. Thank you very much.
Out of curiosity: Why would an app manufacturer do that?
Would you do that with BTT so that users have to re-import all triggers? What's the point?
the bundle id is not necessarily related to the data.
I think maybe it is related to paid version updates where they still want to support the 3.xx version.
Ah, yes, that's the case with DT. DT 3 continues to receive minor updates, even though version 4 is already available.
