Can you once check the properties of your component in /apps.See if you find any anomalies 

Can you check if you have a jcr:lastModified property in your component, ideally there should not be

Are you trying to add/modify the jcr:lastModified via component code ?Ideally dont do that. Also, create a new page and try adding the component to the page, that will rule out of the issue is with the component or a one of issue with the page/template itself.

Are you facing this on your local AEM instance?Can you try removing the jcr:lastModified node from the crx manually.

This happens when URLs are created but not encoded correctly.Try usingURLEncoder.encode(url.toString()); 

Yes, we did. The error remains exactly the same

We have to upgrade the mockito version to atleast 3.4 or any higher. However the moment we upgrade it all test cases start breaking : Page page = aemContext.create().page("/content/testPage"); with error  java.lang.IllegalArgumentException: Illegal page name.   This is what our pom looks like after ...

The bundleContext reference is part of static method, and mockito 3.3 doesnt allow mocking of static methods. Any higher version of mockito is not compatible with aemContext.   Can you elaborate more please, it will help us.

We have a common Utility class, which has following method  public static ResourceResolver getServiceResourceResolver(String subServiceName){        final BundleContext bundleContext = FrameworkUtil.getBundle(Util.class).getBundleContext();       final ServiceReference factoryReference = bundleConte...

We want to remote push to  AEM cloud repo