Skip to main content
S
Siegfried21965884bfck
Participant
April 30, 2022
Question

Error: sdkDeprecation.action must be a string

  • April 30, 2022
  • 1 reply
  • 211 views

Recently, various plugin functions throw an error

"sdkDeprecation.action must be a string"

This is especially the case for

  • Canon Print Studio Pro Version 2.2.3.0
  • CaptureTime to Exif Version 2.4
  • Any Filter Version 1.48.0
    (Only function "Fix Burst Times". The others work)

To exclude an influence of a specific plugin, I deactivated all but one plugin.
Then, I get the error for any of the above mentioned plugins.

Therefore, I assume that it is not a specific plugin which causes the error.

Also, at least the Canon Print Studio worked with previous Lightroom Classic version. Actually, I do not know, with which version it stopped working

 

My environment is:

  • Lightroom Classic Version 11.3.1
  • Camera Raw 14.3
  • Windows 10
This topic has been closed for replies.

1 reply

johnrellis
johnrellis
Legend
April 30, 2022

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

I've never seen that error before.  Capture Time To Exif and Any Filter's Fix Burst Times both use similar SDK actions to run the Exiftool utility and save/read files' metadata.  It wouldn't surprise me if this is more fallout from the bug-ridden changes made to LR 11.3 to cache metadata in the Helper.lrdata file.

 

I'm not able to reproduce the issue yet, so more information from you about Fix Bursts would be very helpful. Please email me the following information to the support email address for Any Filter:

 

1. A screenshot of the error you see.

 

2. Do File > Plug-in Manager and select Any Filter. Click Show Debug Log, which will open File Explorer on the file "debug.log".  Email me that file.

 

 

3. Scroll the right column to the bottom to Plug-in Author Tools. If there are any diagnostic messages, please do Save Diagnostic Log To File and email me that file.

 

Thanks very much.

 

S
Siegfried21965884bfckAuthor
Participant
May 16, 2022

Since the same error showed up also in other plugins, such as LRTimelapse, I had to seriously try to get rid of it.

After all other attempts failed, I succeeded with the following:

After manually adding the different plugins, the error no longer occured.

johnrellis
johnrellis
Legend
May 16, 2022

Glad you got it resolved, and thanks for posting the details -- that might help someone else who stumbles over this obscure error.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices