1

I faced with such kind of exception during our beta package installation:

Missing Organization Feature: Tagging

Looks like Tags are enabled in Setup -> Customize -> Tags -> Tags Settings

What could be the reason?

Improve this question

1 Answer 1

Reset to default
0

If your app doesn't require it as a mandatory prerequisite, in your packaging Org you should not activate features in setup or refer to objects in apex.

You can see all dependencies before upload. My strategy is to work hard keeping that list close to zero. Reason is, once you have that dependency in a release, it might be very hard (sometimes even impossible) to get rid of it again.

Since you are in beta and haven't released it yet you might be able to remove the dependency by

  • disabling the feature
  • remove any direct access to it's objects from apex (if there is any, the platform will nag you in step 1)
  • upload the package again

If you can't deactivate it or can't get rid of a dependency a last resort is to migrate to a new packaging Org. This has a huge downside, since you might have to repeat an earlier security review (and pay plus wait again). So keep an eye on the dependency list before you upload a non-beta release.

Improve this answer

You must log in to answer this question.

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