Hi @moiezma
1.If you're unable to manually clear the /etc/clientlibs folder on the production Dispatcher server, and the standard methods like using the /libs/granite/ui/content/dumplibs.rebuild.html?invalidate=true URL aren't working, you might need to consider alternative approaches. Here are a few options:
2.Dispatcher Flush Rules:
Ensure that your Dispatcher is properly configured to handle flush requests. Check the dispatcher.any configuration file for rules related to flushing. Confirm that the rules are correctly set up to invalidate and remove the /etc/clientlibs cache.
3.Custom Flush Agents:
You can set up custom flush agents or scripts on your authoring environment. When a change is made in CRX or when you publish a React SPA page, trigger these custom flush agents to notify the Dispatcher to clear the /etc/clientlibs cache.
4.Automated Deployment Tools:
If you are using automated deployment tools such as Jenkins or Ansible, you can integrate a step to trigger a cache flush on the Dispatcher after a successful deployment.
5.Dispatcher Flush Scripts:
Consider creating a custom script that can be executed on the Dispatcher server to clear the /etc/clientlibs cache. This script could be triggered remotely, but make sure it's secure and only allows authorized users to execute it.