4

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? – bigassforce Jun 13 '16 at 8:53
  • It fixed a few, but sadly not all - case in with SF now, cheers – Phil Hawthorn Jun 13 '16 at 8:54
  • What's the error in packaging org if you attempt (without changing it) to save a class? – bigassforce Jun 13 '16 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) – Phil Hawthorn Jun 13 '16 at 9:47
  • 1
    Try to re-install the same version of your installed package. This worked for me. – Vrakmhare Jun 14 '16 at 16:20
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. – Phil Hawthorn Jun 23 '16 at 10:42
0

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

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

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.