joao-carloto
commented
8 years ago This situation is happening because the Robot Framework reports are being written inside the extension folder. Basically, the extension architecture and the signature process are incompatible. The current workaround, for now, will be to NOT run tests directly form the browser, or keep reinstalling the extension.
Will try to fix this once I have the time.
Transcrip of an email to a Mozilla editor
My email:
"I hope It's appropriate to contact you directly. If not, please apologize. The FireRobot extension, signed by you a few months ago, is being automatically disabled by the browser, although it was downloaded on the Mozilla website (see attached screen shot). This happens every few days and I have to install it again form the website. I really can't figure out what's going on and I fear this is affecting other users. Can You give an explanation for this?"
Answer:
This issue is because your addon is modifying the contents of your folder. Your addon is set as "unpack" true in install.rdf and you might save data in your addon folder, is this true? As soon as any data in that folder changes, then the signature becomes invalid and the addon gets disabled. We recommend you save data to a folder in the profile folder, and delete it as soon as possible, or on uninstall of addon. The simple-storage module of addon sdk does exactly this. It saves to profile folder/jetpack/addon-id/here - https://discourse.mozilla-community.org/t/does-simple-storage-work/6724/13?u=noitidart