Skip to main content
Participant
April 3, 2019

P: Unable to "Export As"with selection active

  • April 3, 2019
  • 9 replies
  • 203 views

If you use "Export As" while a selection is active it is unable to process the Export. If you deselect and try again everything works fine. This bug happens every time for me.

This topic has been closed for replies.

9 replies

Legend
November 15, 2019
Different issue

Please reference the new conversation here: Photoshop 2020: Program error using Export As scaling to 50%
Legend
November 15, 2019
The original issue posted on this thread should be fixed in the current version, Photoshop 2020 v21.x or later. Let us know if you're still having trouble.
Inspiring
November 15, 2019
Hello, mine is having this issue. Gives me the error when I'm doing "export as" for JPG and I want to be 50% scale. It works when I'm at 100% scale. I have photoshop CC 2019 21.0.1.
BillyBilsAuthor
Participant
April 3, 2019
You're welcome - happy to help!
David Mohr
Participating Frequently
April 3, 2019
Howdy Gary,

Thanks!  That was the missing element.  Yeah, when I scale to 200%, I'm now seeing the same thing on both Win and Mac.  I've gone ahead and logged this. 

Thanks for letting us know!
David
BillyBilsAuthor
Participant
April 3, 2019

BillyBilsAuthor
Participant
April 3, 2019
Have upgraded (20.0.4) and the issue is still there - but I didn't describe fully. It's when resizing in Export As. Have tried different resolutions (high/low) and problem is the same. The file needs more than Background layer to show problem.
Just a little edge case bug as I say - not a biggie but would be nice to have fixed.
BillyBilsAuthor
Participant
April 3, 2019
Whoops... I'm behind an update. Sorry. I'm getting it on Win 10 Photoshop 20.0.3 and have been having the problem for a while. Plenty of space and no problems exporting when no selection. Am updating now and will report back.
David Mohr
Participating Frequently
April 3, 2019
Howdy Gary,

Which OS are you seeing this on?  Latest version of Photoshop?  I ask, because I just checked both Win and Mac, but couldn't reproduce this.  Could this be an issue with HDD space or rights?

Thanks,
David