Hi   Most likely, there is an incorrect selector in your code, or the resourceType is not being captured correctly. Since we don't have the HTML, it's impossible to say exactly what’s wrong. Your best option is to debug it yourself, simply add a "debugger" statement in the code, and open the browser...

Hey, I'm not sure if this will help, but you're filling out a form from Thailand. Try checking out the US (global) page, and then use the "Adobe Assistant" to schedule a call directly with a sales rep. The "Adobe Assistant" will appear a couple of seconds after you load the page, so be patient.   H...

Hi, Can you elaborate on which technology are you using for the mobile app? 

Hi,   I believe you've answered your own question. The GitHub repo contains the official information and available functionality at the moment. You can always open a GitHub issue to propose new ideas.   Hope this helps!

Hi   What is the error you are seeing? From what I can see in the GitHub issue, I will try to update to the latest aio-cli and check once more    

Hi, Please check these resources: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding#splunk https://blog.arborydigital.com/splunk-setup-aem-cloud-service-aemaacs

Hi, Please check here the details about log-forwarding for Splunk: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding#splunk    Also a good resource: https://blog.arborydigital.com/splunk-setup-aem-cloud-service-aemaacs    Hope ...

@mo76 I think you did not understand what @kroyal12 explained, you are not defining a runmode for "preview", you won't have something like "config.preview", instead, you are defining an Environment Variable which will change its value only in the preview environment, please read carefully here: http...

Hi,   I have never encountered this issue before, and since it is not reproducible on your local setup, it must be related to your Dev environment. I would suggest pulling the configurations from the Dev environment into your local to ensure they are not the cause of the problem.   Hope this helps.

Hi @julkarna    The problem is that localization works only when the content tree structure matches exactly the same as the XF tree structure. In the images you shared, it's clear that the trees do not align. Specifically, you have /content/france/french on one hand, versus /content/experience-fragm...