Angular DevTools not available - Firefox Developer Edition about angular

[dgp1130]

Just to update here, it seems that all our extension versions on Firefox got retroactively rejected. This seems to have happened slightly before the 1.0.12 release, so it appears to be an unrelated action by Mozilla.

We got an email about this rejection and warning the builds would be taken down in 14 days, but unfortunately the email went to address which gets a lot of spam and we just missed it. That email stated that reviewers weren't able to verify the build (Mozilla requires applications with build processes to submit their source code and instructions on how to build it). I suspect the issue was just using the wrong Node version for the build.

I resubmitted the extension yesterday with more detailed instructions for building, but unfortunately I haven't heard anything back yet. At this point, we're waiting to see if this version gets approved and can be relisted.

The one fix we can make is updating the account email so we actually see it when something goes wrong in the future.

[wali-valeo]

I have the same problem, I was going to open the issue just now

[dgp1130]

Sorry about this, I published a new version last week, but it seems like it didn't go through properly. The extension page still exists but is not public apparently? I'll need to do more digging and figure out what's going on here.

[COLAMAroro]

As a workaround, maybe someone could publish the .zip file containing the extension, allowing it to be installed manually ?

[Poya-Faraji]

I had this installed on my Firefox and it was working fine unfortunately I deleted it now and I need it badly since I use Firefox as my main testing and development ground. Any updates that when can it be available again ?
Maybe I should try using "https://github.com/bnpoirier/foxify" 😕.

[danielalexis]

Any updates on this matter?

[novikov1337danil]

We are looking forward to any news

[dgp1130]

The add-on is still in review. One reason this has taken so long is that I misread the Add-On store UI and thought I had resubmitted the extension for re-review, but actually had not. I did another release when I discovered this and only just today was that review rejected with boilerplate language "Source code or instructions missing". I'm pretty sure I uploaded the source code correctly and the README includes instructions to build, so I'm not clear on what went wrong there. I've reached out for more info and will follow up with whatever we need to do to get this published.

Unfortunately I don't have any more insight into a timeline for a fix here. We just need to continue to push through with the review process.