Custom Lib for cq.authoring.editor.sites.page &&&&& cq.authoring.editor.sites.page.hook

[SupportMember]

We have installed custom javascript for the editor.html > Granite UI via

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
   jcr:primaryType="cq:ClientLibraryFolder"
   dependencies="[cq.authoring.editor.sites.page]"
   categories="[cq.authoring.editor.sites.page.hook]"/>

We have installed in on development-AEMaaCS, and it works. When we push the same code to staging-AEMaaCS, it is not working. How can we solve this problem. We directly reviewed the cq-authoring.js that is produced on the editor.html.
Reviewing the cq-authoring.js on development-AEMaaCS, our changes are there

Reviewing the cq-authoring.js on staging-AEMaaCS, our changes are NOT there

How would we properly refresh the cq-authoring.js on staging-AEMaaCS, so we can see our changes as expected?

[EstebanBustamante · Accepted solution]

Hi,

The environment will automatically refresh and deploy your code, so you should not have to do any sort of "refreshing". Please double-check if you have pushed the correct code (if the hash associated with the deployment is correct). Also, make sure your page is not cached through the browser (try in an incognito window).

Hope this helps

[Imran__Khan]

Please reverify file changes, location and check filter.xml having file path with override. Try to validate the same in local instance. I hope we are verifying file through crx/de else it will be cache issue.

[kautuk_sahni]

@SupportMember Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.