AssetDelivery is null in some AEM environments | Community
Skip to main content
V
Vignesh_Naren
New Member
September 16, 2025
Solved

AssetDelivery is null in some AEM environments

  • September 16, 2025
  • 2 replies
  • 5606 views

Hi AEM Community,

I'm implemented web optimized URL feature of Dynamic Media for custom components.

I'm following the documentation to create a proxy OSGi service that can deliver web optimized images. https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/advanced/web-optimized-image-delivery-java-apis

 

The code is deployed to all AEM cloud environments.

 

Now the code works on lower environment like DEV and RDE which are using the same Company root folder. Example: companynamedev

But AssetDelivery is retuning "null" in higher environments like STAGE and PROD which are using same Company root folder. Example: companynameprod

 

Any help in debugging and fixing the issue is highly appreciated. 

 

Thanks.

 

 

Best answer by EstebanBustamante

Hi @vignesh_naren 

 

Could you check the logs to see if any errors are being logged?
Based on my experience, the sample code you shared can run into issues on the following line when assets have spaces in their names, since the "seoname" field doesn't allow spaces:

 

options.put("seoname", StringUtils.defaultString((String) options.get("seoname"), asset.getName()));

 

Reviewing the logs should help confirm if that’s what's happening in your case.

 

Hope this helps!

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
September 19, 2025

Hi @vignesh_naren 

 

Could you check the logs to see if any errors are being logged?
Based on my experience, the sample code you shared can run into issues on the following line when assets have spaces in their names, since the "seoname" field doesn't allow spaces:

 

options.put("seoname", StringUtils.defaultString((String) options.get("seoname"), asset.getName()));

 

Reviewing the logs should help confirm if that’s what's happening in your case.

 

Hope this helps!

Esteban Bustamante
    A
    Abie
    Level 4
    September 22, 2025

    Hi @vignesh_naren 


    Is your Stage and Prod pointing to the same Dynamic Media instance as that of Dev?

     

    Thanks!

      Terms & ConditionsAccessibility statement

      Loading footer...