function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
John De SantiagoJohn De Santiago 

active invalid at this location

I came across this issue when deploying my triggers to production. The resolution was that under the Project menu in Eclipse make sure Build Automatically is turned off (unchecked), otherwise the fix will get overwritten before you have a chance to deploy.

Once you do this go to the trigger-meta.xml file for your trigger and remove the Active element from the xml and save. You should be able to deploy with out an issue.

This is what worked for me. Hope it helps anyone with the same issue.