Anyone come across this issue, and if so, find a fix? These are a list of managed classes (installed package) that you are greeted with upon accessing the package within another packaging org.

enter image description here

I would guess this is after the Salesforce upgrade over the weekend.

  • Compile All Classes have any effect? Commented Jun 13, 2016 at 8:53
  • It fixed a few, but sadly not all - case in with SF now, cheers Commented Jun 13, 2016 at 8:54
  • What's the error in packaging org if you attempt (without changing it) to save a class? Commented Jun 13, 2016 at 8:56
  • 1
    No error, does nothing at all (the classes it is complaining about are in an installed package in the packaging org) Commented Jun 13, 2016 at 9:47
  • 1
    Try to re-install the same version of your installed package. This worked for me.
    – Vrakmhare
    Commented Jun 14, 2016 at 16:20

2 Answers 2


To this problem, Salesforce has provided a button 'Recompile All' on the page where the 'Bad References' error is thrown. I clicked on the button to recompile all the classes and I was able to open my package components without any issues. Thereafter the error isnt thrown and the list of package components open as before.

  • 1
    This seems to work in most cases, but not in all. Commented Jun 23, 2016 at 10:42
  • I got a list of thirty or so classes when I tried to Save a new package. But after removing some extensions from Chrome, the "Recompile All" button worked quickly and my Package saved OK.
    – ElHombre55
    Commented Oct 18, 2022 at 20:48

This turned out to be a bug, which Salesforce have now fixed.

Removing and re-installing the package causing the issues also worked.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .