Yes, Deploying a bundle (software package) built with Java 11 to an AEM instance running Java 8 can cause problems. Java 11 has new features and changes that Java 8 doesn’t recognize, so this could lead to errors. AEM bundles compiled on Java 11 to an AEM instance running on Java 8 will indeed cause...

From my experience, you can do this in 2 ways.1. New AEMaaCS Code Deployment, https://sourcedcode.com/blog/aem/how-to-clear-flush-aemaacs-cache-after-code-deployment?swcfpc=1 2. Adding dispatcher cache rules. I'd like to watch how the Adobe WKND project setup rules, and so we can see a rule here   ...

Weird, is this AEMaaCS? if it his, shoot Adobe a support ticket.

Q: Can you please provide the code that is doing this change. How can i add this "Sign in with Adobe" to my local.As an AEM developer on your local machine, you should ALWAYS sign in as username: adminpassword: adminThis gives you the full capabilities of an admin to implement AEM solutions for what...

I would review client-side code like JavaScript and review wether its code from your clientlibs, third-party, or Adobe Launch scripts that may be causing the issues. 

We just got out of this challenging problem as well. Jumped into a call with Adobe, and pinpointed the problem. The problem here is that the latest AEM Core Components introduced this bug.   Let's take a look at what I am pointing to here, so what was removed was the ability to have customers set w...

I got a code snippet laying around that you can try: import static org.junit.jupiter.api.Assertions.*; import static org.mockito.Mockito.*; import com.day.cq.tagging.Tag; import com.day.cq.tagging.TagManager; import com.day.cq.wcm.api.Page; import com.day.cq.wcm.api.PageManager; import io.wcm.testi...

When using the wcm.io mocks library in your JUnit5 tests for AEM, ensuring that cq:tags are correctly retrieved requires proper setup of the mock objects and their properties. Here's how you can make sure cq:tags are correctly mocked and accessible in your tests. Steps to Mock cq:tags Property Corre...

Resolving tags in AEM can sometimes encounter issues due to configuration differences between author and publisher instances, or due to differences in the content repositories. Here are a few steps you can follow to troubleshoot and resolve this issue: Steps to Troubleshoot and Resolve Tag Resolutio...

Looks like you may have tampered with the replication agents on your local machine. You'd need to ensure that you are pointing to the correct AEM instance for example 4503.