P: Couldn't apply Content Credentials error when exporting to google drive from publish services

[Valokammi]

Using Publish services publishing to Google drive streamed folder in physical drive (not virtual drive) and folders that used to publish are usable offline.

When Content Credentials are disbled upload works fine. Enabling Content Credentials (any method) causes errors and files are not uploaded. All file requirements are ok.
Exporting photos normally (not via publish service) with Content Credentials enabled to "normal" physical folder works fine.

[Rikk Flohr: Photography]

Please go to Help>System Info… and provide us with your software's installed version number. 

[Valokammi]

Ah, forgot!

Lightroom Classic version: 14.4 [ 202506051112-5918896a ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.19045
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3,5GHz
SqLite Version: 3.36.0
CPU Utilisation: 7,0%
Power Source: Plugged In, 100% (Charging)
Built-in memory: 16136,7 MB
Dedicated GPU memory used by Lightroom: 743,5MB / 4044,9MB (18%)
Real memory available to Lightroom: 16136,7 MB
Real memory used by Lightroom: 2183,9 MB (13,5%)
Virtual memory used by Lightroom: 3354,7 MB
GDI objects count: 979
USER objects count: 2480
Process handles count: 2660
Memory cache size: 121,7MB
Internal Camera Raw version: 17.4 [ 2272 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 83MB / 8068MB (1%)
Camera Raw real memory: 95MB / 16136MB (0%)

<edited>

[Rikk Flohr: Photography]

Thanks, I will look into it. 

[Valokammi]

Update! Suddenly LR didn't export nothing when Content Credentials enabled. LR looks like it is exporting. It creates tmp folder to export folder (which I think is empty whole export process). LR Delete tmp folder after "export" and throws an error.

So I reset preferences and now it seems to work.
Update 2! After reset Content Credentials enabled exporting to normal way works. But export to G-drive folder throws an error as before.
Sometimes I feel this is related to moon phase 😄

[Rikk Flohr: Photography]

We haven't been able to replicate this failure on our end. The Dev has asked if you can provide detailed, step-by-step instructions for how to do so. 

[Valokammi]

Ok. Here's details that I can give. I put somekind ofg screenshot of what is happening. LR preferences are reset.
Google drive setup: Streamed to local hard drive folder, not virtual drive. Folders that are used to export are set offline use.

Lightroom Publish services: Create Publish service for hard drive and point it to folder in Google drive folder (spefic folder). I set everything else by what is needed, all setups works well when Content Credentials are disbled.

When I enable Content Credentials (only Producer info and tested all variations of attaching)  and hit Publish, it creates tmp folder in export folder, but it disappear after export leaving folder empty and LR throws an error (Couldn't apply Content Credentials.). 

Lightroom export: When exporting to hard drive normally Content Credentials enabled, no errors. Tested export to G-drive folder Content Credentials enabled, not work, disabled it and photo is rendered.

I have LR installed at my home too (same subscription, all apps up to date in both pc) with same kind of problems (reset preferences too). At home I have Windows 11.
BUT in windows 11 when I try to use publish service to Google drive (G-drive configuration same as work, streamed offline folders) folder Content Credentials enabled sometimes I can see individual jpg files showing and disappearing in folder.

[Valokammi]

I got email from Sunil "I am from Adobe, responding to your feedback about Lightroom Classic. Could you please get us the console log to investigate?"

Reproduced issue by normal export to g-drive and log file is empty.

[Valokammi · Accepted solution]

I think I got it! If root folder or subfolders contains scandinavic letters like ä and ö, export with C&C  enabled fails! Google drive root folder for clients is "Asiakastyöt" and exporting with C&C enabled fails even if subfolder doesn't contain scandinavic letters.
Update! Got email from Adobe and they confirmed problem in windows and are investigating it. So I mark this solved.

[Robert_45]

Message :

Bonjour,

J’utilise Lightroom Classic (version 14.4) et j’ai constaté un comportement anormal lors de l’exportation d’images JPEG avec l’option Content Credentials activée.

Lorsque le chemin d’exportation contient des caractères accentués (comme é, è, à, etc.), l’export échoue systématiquement avec le message suivant :

Impossible d’appliquer les Content Credentials. (1)

En revanche, si le nom du dossier ne contient aucun accent ni caractère spécial, l’export se fait normalement, et les Content Credentials sont bien intégrés.

Cela semble indiquer un bug dans la gestion des encodages ou une limitation côté infrastructure Adobe. Ce point pourrait gêner beaucoup d’utilisateurs non anglophones ou dont les chemins de fichiers contiennent des caractères régionaux.

Merci par avance pour votre attention à ce problème .

Cordialement

[Claire H.]

Hi @Robert_45, Welcome to the Lightroom Community forum! Lightroom Classic generally supports most Unicode characters, which should include accented characters. To better help you with this issue, we would like a few more details. Can you send your system info, a screen recording of your issue, and a numbered list of the exact steps needed to replicate the issue? You can find your system info by going to Help > System Info, copying and pasting it into a text file, and attaching it here. Thanks! ^CH

[Kaja29616689iumb]

Hello. Same problem here with polish characters like "ł" "ó" "ż" and so on. Lightroom couldn't finish export, "lightroom couldn't apply content credentials". Problem solved after changing names of folders, including master folder, so they don't have specific polish characters in names. Just to let you know that it is problem with another language too.

[Valokammi]

Looks like it is fixed in version 14.5. No errors anymore when folder contains ä,ö, etc. characters.