Why in one case I have the Finder and NOT Google Chrome, and in the other I have Google Chrome and NOT the Finder?
Is there a way to force “registering“ an app on the Automation Privacy page?
I have done more than one search on the topic but nothing interesting was discovered.
I noticed on this forum an earlier thread about something similar, but this was a while back when Catalina was just published, and no real answer to the issue was discussed:
Do both computers use the same Chrome versions & preferences? This is a security warning of Chrome, not one of macOS and therefore system preferences do not matter in this case.
One workaround could be to active the Clip to DEVONthink tab of the Sorter and choose Chrome instead of using the extension (or to use the hotkey, see Preferences > Sorter).
Do both computers use the same Chrome versions & preferences? This is a security warning of Chrome, not one of macOS and therefore system preferences do not matter in this case.
thanks for giving me a hint to go and look in the right spot, for some reason I thought it was a Catalina security setting, but it really is a Chrome issue.
I found some links pointing to this piece of doc:
and the issue surfaced sometimes in the last few months, and maybe I had not used this feature on the second machine so I did not notice until today. Still, I don’t have the issue on the other, so go figure!
The fix is a simple terminal command changing a default policy:
and this discussion on SuperUser provided the answer:
and now the issue is fixed.
It would be nice to understand why I don’t have the issue on the other Chrome installation, same OS and same Chrome version, but I think I will pass and just enjoy the result!
I’ve searched all over but can’t seem to find a solution for this solution, meaning that checking the box only keeps it from popping up again on that particular domain. That helps only a little – I’m clipping things to DT3 from all manner of sites and having to click the box AND the Allow button each time I clip from a new one is unnerving.
Has anyone discovered a way to give Chrome universal permission to open DT3 calls?
I just found success resolving that prompt in Chrome by applying the following enterprise policy setting in Terminal. (Credit to Best Mac Tips… DevonThink - Best Mac Tips):