Unable to record actions that run scripts in 25.7.0

[alexanderl16240166]

I have a lot of photoshop actions that run javascript files. They all still run fine in 25.7 but I'm unable to record any new ones. If I record a new one and attempt to run it I get an error "Could not complete the command because Photoshop was unable to find the JavaScript file." 
When I twirl open the details on the "Scripts" action step, it has the correct "File: path/to/file" but unlike in older actions I've recorded there is now a Name:"" (empty quotes). I'm assuming this is what's causing the problem. 
I'm not positive if this behavior changed in 25.7.0 with the new action export changes, or if I just hadn't noticed and it'd been a minor version or two since I'd tried. 

[Jeff Arola]

What version of macOS are you using?

If you go to Apple>System Settings>Privacy & Security>Full Disk Access, is Adobe Photoshop listed?

Another thing to try is a reset of the Photoshop preferences:

https://helpx.adobe.com/photoshop/using/preferences.html

[alexanderl16240166]

I am on macOS 13.6.6, which is the latest version of Ventura. Haven't taken the plunge on Sonoma yet. 

Photoshop did not have Full Disk Access enabled. I enabled it and restarted and it did not make a difference. 

Would rather not reset preferences as of yet as it definitely seems to be a bug introduced in the latest program version since it was working fine until last week when I updated it. 

[Stephen Marsh]

This has recently come up on the forum at least once before.

Can you share a copy of an action with this issue, even if that is the only step.

You may need to install the script files in the apps presets/scripts directory and record their execution that way rather than using browse.

[alexanderl16240166]

Hi Stephen, I tried to attach one but ironically adobe doesn't allow .atn files to be attached, despite having a rather impressive list of other files that can be.. 
Attaching a screenshot of it the actions panel in the meanwhile. 

Is this not the correct place to submit bugs directly to Adobe? Appreciate y'all trying to help, but this seems like an issue in their court.

Edit to add: also all my dozens of existing actions work fine so I'd rather not move my folder of hundreds of scripts into Presets / Scripts. 

[Stephen Marsh]

That "helper" second line is the issue that I can't replicate on my system. Adobe have added similar to actions in the past but this is the first time with scripts. With no official word it's unknown.

What if you record browse to the desktop rather than Dropbox?

Otherwise install the script in the presets/scripts folder so that it can be recorded directly from the scripts menu without using browse.

[alexanderl16240166]

I tried recording it with it on the desktop, which made no difference. I then tried with it in the presets/scripts folder which does indeed work, and the "name" field is filled in with the filename. Hoping an Adobe employee sees this and can get this on the list of things to fix as, again, this was not the behavior until the latest version and very much seems like a bug. 

[alexanderl16240166 · Accepted solution]

Necro-ing my own thread here a bit, but I just figured out why you weren't seeing it. I thought they'd fixed the issue but I just ran into it again in a way that prompted me to test, as I recorded a two step action and one script was fine and the other one wasn't (had this Name: ""). By commenting out the entire problem file and uncommenting one section at a time I was able to isolate the determining factor as being: 

app.doAction("action","set");

 Scripts that have this line are recorded with the ' Name: "" ' bit and cannot be run. If you comment out this line, record the script into the action, then uncomment it, your action will work fine. 

I'll report this bug to Adobe, but wanted to also post this workaround here in case anyone else happens to stumble upon this. 

[Stephen Marsh]

@alexanderl16240166 

Thanks for the update!

[Bojan Živković]

It appears to be a Mac-specific issue. I just tested it, and everything functions correctly on Windows; the script name is recorded as part of the action step and will call the appropriate script upon execution.

[Stephen Marsh]

@Bojan Živković – I'm on an Intel Mac Monterey OS and with 25.7.0 there is no problem for me recording a browsed script on a local drive path... So we may need to isolate this a bit deeper.

@alexanderl16240166 – What OS and chipset (Intel, M1 etc) are you running?

[Stephen Marsh]

Here is the other topic that I have seen from another Mac user, same issue.

https://community.adobe.com/t5/photoshop-ecosystem-discussions/some-scripts-not-running-from-action/...

[Julian315683138kub]

I'm having a similar issue. A simple script of Replace Content seems to not work anymore:

function replaceSmartObjectContent(layer, file) {

    var idplacedLayerReplaceContents = stringIDToTypeID("placedLayerReplaceContents");

    var desc = new ActionDescriptor();

    desc.putPath(charIDToTypeID("null"), new File(file));

    executeAction(sTID('placedLayerReplaceContents'), desc, DialogModes.NO);

}

[Stephen Marsh]

@Julian315683138kub 

Does the action recording using browse record the second line for file?

If not, then it would appear to be a totally different issue and a new, separate topic should be created to correctly diagnose and address your specific issue.