Mac OS 10.15.3, Bridge 10.0.3.138

I haven't been able to generate a PDF from a stack of PSD files for the last couple of versions of Bridge. This worked well in Version 7. (I also tested the same procedure with a stack of JPG and a stack of TIFF files to ensure it wasn't a read error.)

When using a custom template in the Output module, my settings are:
• 2188x2875 px
• 300 PPI
• IQ 10
• 1 Column x 1 Row (one image per page)
• No Margins, filenames, headers, footers, or watermarks

Every attempt to export to a PDF (whether 1 page, 2 pages, or 30+ pages) results in a "This operation could not be completed" error.

After exhaustedly searching Google and the Adobe forums in vain, I decided to find the root cause of the error. I logged the event in my Console, and found a reproducible error. It seems when Adobe started re-writing the app in Swift, UIImagePickerController was more forgiving. However, as of Swift 4+, an execution error occurs if the timing is too close when the completion is set to nil.

The specific error is:

errors encountered while discovering extensions: Error Domain=PlugInKit Code=13 "query cancelled" UserInfo={NSLocalizedDescription=query cancelled}

A probably string in the code looks like:

func imagePickerController(picker: UIImagePickerController, didFinishPickingMediaWithInfo info: [String : AnyObject]) {}

And for Swift 4+ (4.2 or later) that should be written as:

func imagePickerController(_ picker: UIImagePickerController, didFinishPickingMediaWithInfo info: [UIImagePickerController.InfoKey : Any]){}

Alternatively, a one second delay should be sufficient as well:

func imagePickerController(_ picker: UIImagePickerController, didFinishPickingMediaWithInfo info: [String : Any]) {

if let image = info[UIImagePickerControllerOriginalImage] as? UIImage {


    picker.dismiss(animated: false, completion: nil)

    DispatchQueue.main.asyncAfter(deadline: .now() + 1.0, execute: {

        self.discussionImage.image = image

    })

}

}

Since I cannot see the code, also ensure the delegate is set to self by implementing pickerview.delegate = self on viewDidLoad.

I’ve attached the console so you can see the error timing for yourself.

Thank you for fixing this!

Using Bridge v 10.0.0.124. Running on macOS Mojave (because of the laundry list of unresolved problems with AC Raw and Photoshop running on Catalina).
Updated this afternoon and now Bridge won't create Thumbnails or Previews at all.

I've tried purging cache and restarting my computer and Bridge several times.

I get the "(Generating Thumbnails..., Generating Previews...) note on the bottom panel as Bridge would do normally, but even after leaving Bridge open for an hour no new previews are generated. I have a blank grey square where my image preview should be for all images in a given folder. Raw DNG, Jpgs, Raw NEF files, makes no difference.

It's very frustrating that an update will stop a basic function of a file management software. I've lost and afternoon's work on this already.

HELP!

I have just updated my Bridge and Photoshop to their latest versions (November 2019, see detailed version info below).

**** See also update below (Bridge may now use PNGs for thumbnail/preview files in the cache for certain layered PSD files!)

It seems that there are some problems with color management in the new Bridge.
The previous version which I have used until yesterday worked OK. Nothing changed in my system except new Adobe apps today. !!Except: Updated my graphics driver just before Adobe apps (see version info below).

I use Bridge/Photoshop for photography. In Bridge the previews and thumbnails Bridge looks OK for old photos (JPEG, PSD, Raw). However, when editing old PSD files or when creating new PSD documents, the preview for the new files will (often) be wrong. What I observe is about the same effect as I get when I view photos with an application that does not support color management. Since my monitor has a wide gamut LCD panel, the difference is quite pronounced, with oversaturated colors etc.

I have done some experiments and below is a description of a procedure that in my case is able to reproduce the problem with a few simple steps.
Also, when opening a Raw file with "Open Image" in ACR (yielding a flat image in the background layer), the preview in Bridge is OK.
When opening a Raw file with "Open Object" in ACR (yielding a smart object with no background layer), the preview in Bridge is wrong.

The problem can be demonstrated like this:

1) create a new document in Photoshop (try sRGB, color managed first)
2) fill the new document with a solid color (medium bright, medium saturation, I used green)
3) save the document
4) the preview in Bridge looks OK
5) create a new document in Photoshop (try sRGB, color managed first)
6) unlock the background layer
7) make a copy of the layer (yielding two identical layers with a solid color)
8) save the document
9) the preview in Bridge is now wrong (it is easy to see the oversaturated color)

Seems to have something to do with the use of layers?

**** UPDATE: I just found out that it seems that Bridge now erroneously
generates (non-color managed) PNG files for thumbnail and preview files in the cache for certain layered PSD files!!! More info in the posts below.
Have a look at the image files in the cache file location (Windows):

C:\Users\jjoha\AppData\Roaming\Adobe\Bridge\Cache\v36

I tried turning on "Use Software Rendering" in Bridge Preferences, but it did not seem to have any effect on this problem (PNG files still made for files with wrong looking previews).

Version numbers for software/hardware used:

• Adobe Photoshop Version: Adobe Photoshop 2020 Version: 21.0.0 20191018.r.37 2019/10/18 x64


• Bridge Version: Adobe Bridge 2020: 10.0.0.124 x64


• Adobe Camera Raw Version: 12.0.0.322


• Monitor: Eizo CG2730 (calibrated regularly with Xrite i1 Display)


• Windows 10 Pro x64 version: 1903 - Os build 18362.449


• Graphics driver: Driver version: 441.12 (GeForce GTX 1060 3GB)

Just double checked turning on/off "Use Software Rendering" (with Bridge restart/PC reboot). In my case this setting does not seem to have any effect on the problem. Turning on "Use Software Rendering" just makes 100% previews slower to show up.

Also, for the files in question, Bridge still generates PNG files in its cache (which are non-color managed and are shown with oversaturated colors etc. on a wide gamut monitor), for both thumbnails, standard previews and 100% previews. As far as I can see this is new (erroneous) behavior.

To the manager of this project. Please make everyone a favour and resign. Let someone else take over this project. Scratch last 2 years of coding and build on last stable working version from 2018.
I have made a mistake of installing Bridge 2020 after 2019 fiasco. I thought that maybe maybe after another year this version would be usable.
I could not believe my eyes - It is actually even worse!
100% preview is not working - changin photos (cursor) - back and forth - sometimes 100% preview is shows, sometimes some soft version in lower resolution. This applies to 2 files. Keep changing between them you get randomly soft and sharp version.
I worked as software engineer for 15 year. Never saw such incompetence.