Bug Reports

The home screen shows recently opened files listed by "last modified" regardless of whether or not the file has actually been modified, and shows a modification time which is entirely spurious and misleading. It would be better to have an option for "last opened" or "last viewed".

  As you can see, none of the layer thumbs is rendering, and the doc stops working entirely as soon as I toggle visibility on any of the layers. Closing and reopening fixes rendering...until I toggle a layer again. (Or, for that matter, anything else. Even just selecting a tool causes the entire canvas to go gray!) Other docs continue to work fine...for now. This has me spooked, & wary of trusting the app!Anyone know of a way to recover the document?

Adobe Photoshop version: 21.0.1 20191106.r.47 2019/11/06: 3152b481f18  x64OS: Windows 10 64-битOS version: 10 or more 10.0.18362.329sample jsx code app.documents.add(100,100);app.activeDocument.saveAs(new File( "C:\\cloud-content1\\asd.psd")); The folder C:\cloud-content1\ exists and it's allowed to write in this folder.Expected result: file saved to the specified pathActual result: error, approximate translation of message is:Can't save as "/cloud-countent1/asd.psd": file not found.The same error occurs for many variations of the file path, such as C:\\cloud-content\\asd.psd", C:\\cloud-contentasdf\\asd.psd" and so on.When saving manually from the Photoshop UI - works fine.

Hi folks, can anyone advise how to change (what I think are) the annoying thick/fat handles and corners on the crop tool post the 2020 update ? I've posted a picture below of what I mean.Is it possible to alter their size, thickness, opacity etc or even go back to the style in Photoshop CC 2019 ?The problem I find now is that you can't judge the crop properly for fine (small) crops less than the thickness of the handles or where you reference point is under the corner or side handles.Many thanks in advance

Recently, I was using the simplified Chinese version of Photoshop (version 21.1.1), drawing a rectangle, and the software default display unit is 100 像素 * 100 像素. But I want to change it to 100mm * 100mm(or 100毫米*100毫米). When I input 100mm in the size input box, the software directly reports "invalid number item". The size changes, but the unit is not mm but 像素. When I input 100毫米mm in the dimension input box, the software can change normally and the unit is correct. This proves that this version of Photoshop does not support the exchange of Chinese and English units, but the previous versions can. I hope the official can fix this problem,because it's too much trouble to input Chinese for dimension unit.

Scenario: A layer is selected The “select” tool is selected You switch to another app by swiping left on the “handle” at the bottom on the screen in iPadOS You switch back to Photoshop The previously selected layer is moved way offscreen Admittedly, this doesn’t happen every time I do this, but it does happen a lot.

Before PS 2020, layers with shallow Knockout enabled and reduced Flow could be clipped to layer groups. These clipped layers would interact with each other, mainly allowing separate shadows to be added without stacking with each other.When opening the same documents in PS 2020, the clipped layers with knockout give wildly different results. Solid color fill layers blend in Normal mode despite layer blend settings, and cause the attached group to also reduce in Flow, making these areas partially transparent. Regular layers appear to have a per-channel effect, with Flow and Opacity serving completely different purposes from before.When playing with the "Transparency Shapes Layer" setting in Blending Options, it appears that PS 2020 show the previous behavior in preview, but continues to do the unwanted behavior when committing a change. (The setting doesn't actually change the result.)Top left: PS 2019 and Shade 1 shapeTop right: PS 2020 and Shade 2 shapeBottom left: unblended contents o

In common with other users PS now crashes on every occasion when using Content Aware Fill. It was working fine although I haven’t used it for a couple of months. I am currently using the latest version 23.01, but it was the same with the immediate prior version & also with v22.5 when I explored downgrading. The system & drivers are all up-to-date. I have tried all the logged fixes including extending the TDR values & turning off GPU acceleration but to no avail. Logs have been submitted when the box opens. My system is Win 10 64bit 19042.1288, Intel I7 9700K, 32Gb, Aorus Z390 AORUS ELITE, XFX Radeon RX 570, PS 23.0.  

Today I installed update to 22.1.1 version with a hope to find fixed bugs which have been discussed in another thread. But in this version I've found exactly the same bug. Adobe has not fixed it. There are multiple ways how to reproduce this bug. Some of them involve 3rd party filters but it can be reproduced using built-in filters in order to avoid blaming other companies for incompatibility of their filters.   1) Open an image. I've tested it with RAW images from multiple Nikon cameras (d90, d750, z6), but it works also when I create a new document manually (I have tested it with canvas size 4000 x 4000 px).2) Turn rulers on - with rulers turned off, behavior is slightly different3) Select "Adaptive Wide Angle" filter from filter menu.4) After the image preview renders cancel the filter5) Canvas disappears and I only see the recent file list (which is not clickable) or just gray background With rulers turned off (see step 2) Photoshop behaves after canceling the filter as if the

If you open a photoshop document that has missing links that have a file path to a remote/external server. Photoshop slows down significantly. If you switch PSD tabs and switch back it takes around 30 seconds just to load each time. It's as if it continues to search for the links even when you haven't asked it to.

See screenshot...https://screencast.com/t/ehLHK8TX4FWhen exporting this particular file, a bunch of mysterious canvas space is being added.

It used to work fine, but now when I select & mask from a Layer Mask it doesnt now show my adjustments in the preview window. But when I step out of select and mask by pressing 'ok', my adjustments are made. It means Ive no visability of what changes I am making...can anyone help? Could it be memory related? If so how do I fix?  

I added a rectangle shape with round corners.   When I export as JPEG without any scales it exports a expected, however, when I use Export As and set scale to 0.3, the rectangle corners are not scaled properly.   See attached images.  The one with the very round edges is the scaled one. Is this a bug? If not how to scale shapes proportionally?  

macOS 11.5.2 Photoshop 22.5.0   Steps to reproduce the issue: 1. select rectangular marquee tool 2. make a selection in an empty area of the canvas 3. under properties > transform, make any adjustment to W, H, X, or Y 4. an error dialogue box appears 5. clicking "OK" on the dialogue box dismisses it, but it immediately reappears no matter how many times you dismiss it - only option is to force-quit Photoshop   Video: <a href="<a href="<a href="https://www.youtube.com/embed/fxZC8EyUD1E" target="_blank">https://www.youtube.com/embed/fxZC8EyUD1E</a>" target="_blank"><a href="https://www.youtube.com/embed/fxZC8EyUD1E</a&gt" target="_blank">https://www.youtube.com/embed/fxZC8EyUD1E</a&a

When copying an image with a clipping mask from Illustrator, the bounding box is not set to the clipping mask boundaries, but to the boundaries of the clipped image. This makes scaling the image difficult.  I'm not sure if this is an Illustrator or Photoshop problem. I know Illustrator has had problems with masks before and say they have solved it, but the issue still occurs when copy pasting from Illustrator to Photoshop.   https://illustrator.uservoice.com/forums/333657-illustrator-feature-requests/suggestions/20359933-option-to-export-to-clipping-mask-boundaries

Since updating to version 3.2.1 on my iPad yesterday I can no longer change text size properly (or any of the text editing options). The slider works but gets stuck at max 288 font size and I can't tap to edit any of the numbers myself. Anyone else having this issue?

When working with the rotate tool, we have the opportunity to set the angle of rotation of the canvas by entering the desired value on the toolbar, however, if we do the same through the script, the rotation does not occur (bur the specified angle is stored in the current tool settings):     #target photoshop; var s2t = stringIDToTypeID; (r = new ActionReference()).putClass(s2t("rotateTool")); (d = new ActionDescriptor()).putReference(s2t("target"), r); (d1 = new ActionDescriptor()).putInteger(s2t('angle'),99) d.putObject(s2t("to"), s2t("target"), d1); executeAction(s2t("set"), d, DialogModes.NO);     We can assume that the code does not work at all, but if we decide to control the rotateAll parameter in the same way, the change is immediately shown in the toolbar:     #target photoshop; var s2t = stringIDToTypeID; (r = new ActionReference()).putClass(s2t("rotateTool")); (d = new ActionDescriptor()).putReference(s2t("target"), r); (d1 = new ActionDescrip

When the PS theme is switched to light color, the text on Neural Filter progress bar cannot be seen clearly!!This bug hasn't been solved since the first version!!

The menu that pops up while saving a jpg file doesn't show the file size anymore in PS 2022. Now it shows only two dots in stead of the file size. Does anyone know how to fix this?

I have a problem the last few months with using the Wacom pen in Liquify. After I applied the Liquify effect, Photoshop starts being unusable so I have to save my docs and restart. It is worth noting the previous version of Ps worked perfectly. I don't understand why Adobe developers always fix one thing while destroying another thing. If this was the only bug I experienced, it wouldn't be so bad, but I can start counting the bugs in the new releases. As a heavy user, I can't ignore it. 

I have a documented the same problem. No matter where I have the tool bar (not shown here, but in these photos, the toolbar is docked), when I open a photo, it opens up smaller even though I have the screen size to open it larger. What can I do to open the photo at maximum size allowable by space?Note: This conversation was created from a reply on: Photoshop: There isn't enough room to display this document.

Technical info: Photoshop v22.5.5, MacBook w/ Retina Screen, Mac OS 11.6   When I downsize a photo that is a Smart Object, it appears to use Bicubic (Sharper) even when I select "Bicubic (smooth gradients)". To replicate this issue, simply open a high resolution photo, duplicate the background, convert the duplicated layer to a smart object, then reduce the photo by a large amount using "Bicubic (smooth gradients)" for the resample type. Zoom in to 400% and then compare the two layers. The smart object will be sharper than the background layer since it apparently uses Bicubic (Sharper) no matter what resample type is chosen, whereas the background layer was reduced using "Bicubic (smooth gradients)". Here is an image that shows what I am talking about using the exact instructions mentioned above: The raster background layer is on the left, and the smart object layer is on the right. The image is a screenshot of the image zoomed to 400%.

I'm resizing an artboard from 600x1200 to 50%.     It results in 301x600 instead of 300x600.   See my screenshared video here.   Thank you

The internal browser does not allow the go back to a previous page. This thing is not ready for production. Open an external safari with full controls.

I updated from Photoshop CC 2018 to CC 2019 a few weeks ago.Since then I have maybe three crashes and none of them auto-recovered anything.I imported my settings when updating from CC 2018, and I've also double checked that my Preferences have Auto-save on, set to every 5 minutes.The only thing a search turned up is this conversation from 4 years ago:https://feedback.photoshop.com/photoshop_family/topics/how_to_recover_an_auto_saved_file_when_photos...That is a much older version of Photoshop, but as in that discussion I do have my scratch disk set to my 😧 drive instead of the C: (boot) drive.I had occasional crashes or hard shutdowns in CC 2018, and had files successfully recovered, so if it is the scratch disk location problem mentioned in that old conversation, it seems to be a bug that has come back from the dead.I will try switching my scratch disk to my C: (boot) drive and wait for another crash and see what happens.Pretty aggravating, losing hours of work.