Vjylku

Making him into a bully (how to show mild violence)

Why don't hotels mount air conditioning units outside the rooms?

What is the purpose of easy combat scenarios that don't need resource expenditure?

Does Skippy chunky peanut butter contain trans fat?

Is there a Linux system call to create a “view” of a range of a file?

Can we harness gravitational potential energy?

What are "industrial chops"?

What to look for when criticizing poetry?

False written accusations not made public - is there law to cover this?

Why am I able to open Wireshark in macOS without root privileges?

How should I handle players who ignore the session zero agreement?

Can I make estimated tax payments instead of withholding from my paycheck?

Why would space fleets be aligned?

Dilemma of explaining to interviewer that he is the reason for declining second interview

Calculate the number of points of an elliptic curve in medium Weierstrass form over finite field

What's a good word to describe a public place that looks like it wouldn't be rough?

Difference between i++ and (i)++ in C

Why are the books in the Game of Thrones citadel library shelved spine inwards?

Cat is tipping over bed-side lamps during the night

Why zero tolerance on nudity in space?

How old is the day of 24 equal hours?

Has any human ever had the choice to leave Earth permanently?

Non-Cancer terminal illness that can affect young (age 10-13) girls?

How much mayhem could I cause as a sentient fish?

Salesforce package error error “You can't specify version for namespace sf_com_apps because this namespace is not installed to your organization.”

Can a managed package cease to depend on another managed package?Managed app installation on Salesforce Production OrgWhen building a package with a dependency how is the minimum version of the dependent package determined?Why does code coverage consider pre-installed packages?When does it make sense to add a Connected App to a Managed Package?Does post-install script run when a patch version of the package is installed?From inside a Salesforce packaging org, how do you query the list of created versions for a managed package?What namespace to use when developing Lightning components for a managed package?How to specify namespace and partition for Org Cache when creating managed package?Is there a way to figure out how a previously installed package was installed when upgrading?

1

I'm having an odd issue where a package I've been maintaining for a while has now decided it is dependent on Salesforce Connected Apps (namespace sf_com_apps). Even when I try to remove the dependency by editing the metadata of the pages, components and lightning components it's being automatically added back. I don't believe any of my code is actually using anything from this package and I don't want my users to have to install it (as there isn't an easy way to do it, you seem to have to log into the org through workbench for it to install).

The only thing I can think that might have had something to do with this is upgrading API versions for all my code to 45.

The error the org will receive if installing my package but sf_com_apps doesn't exist is: "You can't specify version for namespace sf_com_apps because this namespace is not installed to your organization."

managed-package

share|improve this question

edited 2 hours ago

Matt Lacey♦

20.9k547120

asked 3 hours ago

Kenji776Kenji776

285412

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.
  
  – Matt Lacey♦
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So packages always have this dependency now? Like all packages created now will have this error if sf_com_apps isn't installed?
  
  – Kenji776
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I wasn't sure where it was coming from tbh, but workbench makes sense. It's not always a dependency.
  
  – Matt Lacey♦
  1 hour ago
  

  
  
  
  

add a comment | 

1

I'm having an odd issue where a package I've been maintaining for a while has now decided it is dependent on Salesforce Connected Apps (namespace sf_com_apps). Even when I try to remove the dependency by editing the metadata of the pages, components and lightning components it's being automatically added back. I don't believe any of my code is actually using anything from this package and I don't want my users to have to install it (as there isn't an easy way to do it, you seem to have to log into the org through workbench for it to install).

The only thing I can think that might have had something to do with this is upgrading API versions for all my code to 45.

The error the org will receive if installing my package but sf_com_apps doesn't exist is: "You can't specify version for namespace sf_com_apps because this namespace is not installed to your organization."

managed-package

share|improve this question

edited 2 hours ago

Matt Lacey♦

20.9k547120

asked 3 hours ago

Kenji776Kenji776

285412

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.
  
  – Matt Lacey♦
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So packages always have this dependency now? Like all packages created now will have this error if sf_com_apps isn't installed?
  
  – Kenji776
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I wasn't sure where it was coming from tbh, but workbench makes sense. It's not always a dependency.
  
  – Matt Lacey♦
  1 hour ago
  

  
  
  
  

add a comment | 

I'm having an odd issue where a package I've been maintaining for a while has now decided it is dependent on Salesforce Connected Apps (namespace sf_com_apps). Even when I try to remove the dependency by editing the metadata of the pages, components and lightning components it's being automatically added back. I don't believe any of my code is actually using anything from this package and I don't want my users to have to install it (as there isn't an easy way to do it, you seem to have to log into the org through workbench for it to install).

The only thing I can think that might have had something to do with this is upgrading API versions for all my code to 45.

The error the org will receive if installing my package but sf_com_apps doesn't exist is: "You can't specify version for namespace sf_com_apps because this namespace is not installed to your organization."

managed-package

share|improve this question

edited 2 hours ago

Matt Lacey♦

20.9k547120

asked 3 hours ago

Kenji776Kenji776

285412

share|improve this question

edited 2 hours ago

Matt Lacey♦

20.9k547120

asked 3 hours ago

Kenji776Kenji776

285412

share|improve this question

edited 2 hours ago

Matt Lacey♦

20.9k547120

asked 3 hours ago

Kenji776Kenji776

285412

edited 2 hours ago

Matt Lacey♦

20.9k547120

edited 2 hours ago

Matt Lacey♦

20.9k547120

asked 3 hours ago

Kenji776Kenji776

285412

asked 3 hours ago

Kenji776Kenji776

285412

2 Answers
2

active

oldest

votes

3

You can't directly "undo" a dependency once you upload a "released" version that causes the dependency. What you need to do is open a case with Partner Support and request that they roll back all versions that caused the dependency to "beta," at which point you should be able to fix the problem. This will involve uninstalling all affected versions from any orgs they are installed in. It would be ideal to uninstall/delete any apps that should not be in your org, as that can cause packaging issues (as you've unfortunately discovered).

share|improve this answer

answered 2 hours ago

sfdcfoxsfdcfox

257k12201444

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Awesome, thank you for the info. What I suspect happened is when I copied all my code from my dev into the packaging org the SF connected apps dependency got somehow included. This is going to sound really dumb, but since this is a developer org I'm not able to open a case from that account. How would I go about logging a case with them for this org?
  
  – Kenji776
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Kenji776 If you're an ISV, you'd just log a case through your ISV account. If not, there's probably nothing you can do about it short of building a new package. Managed packages are not to be trifled with, they are very finicky.
  
  – sfdcfox
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'd log something through the partner portal and provide the org ID. Good luck though.
  
  – Matt Lacey♦
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Alright, thanks guys. I'll see about getting a case opened. This package is being developed for a client and they already have a released version that went through security review and all that so building a new package is all but off the table. Lets hope support can help fix this mess or else I'm hosed.
  
  – Kenji776
  1 hour ago
  

  
  
  
  

add a comment | 

0

I was actually able to find a fix for this. I uninstalled the Salesforce Connected Apps package which removed the reference to it in all my code. I was then able to upload a new version of the package which did not have the dependency and hence no error! Thanks @sfdcfox for pointing me the right direction!

share|improve this answer

answered 35 mins ago

Kenji776Kenji776

285412

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f252011%2fsalesforce-package-error-error-you-cant-specify-version-for-namespace-sf-com-a%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

You can't directly "undo" a dependency once you upload a "released" version that causes the dependency. What you need to do is open a case with Partner Support and request that they roll back all versions that caused the dependency to "beta," at which point you should be able to fix the problem. This will involve uninstalling all affected versions from any orgs they are installed in. It would be ideal to uninstall/delete any apps that should not be in your org, as that can cause packaging issues (as you've unfortunately discovered).

share|improve this answer

answered 2 hours ago

sfdcfoxsfdcfox

257k12201444

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Awesome, thank you for the info. What I suspect happened is when I copied all my code from my dev into the packaging org the SF connected apps dependency got somehow included. This is going to sound really dumb, but since this is a developer org I'm not able to open a case from that account. How would I go about logging a case with them for this org?
  
  – Kenji776
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Kenji776 If you're an ISV, you'd just log a case through your ISV account. If not, there's probably nothing you can do about it short of building a new package. Managed packages are not to be trifled with, they are very finicky.
  
  – sfdcfox
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'd log something through the partner portal and provide the org ID. Good luck though.
  
  – Matt Lacey♦
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Alright, thanks guys. I'll see about getting a case opened. This package is being developed for a client and they already have a released version that went through security review and all that so building a new package is all but off the table. Lets hope support can help fix this mess or else I'm hosed.
  
  – Kenji776
  1 hour ago
  

  
  
  
  

add a comment | 

3

You can't directly "undo" a dependency once you upload a "released" version that causes the dependency. What you need to do is open a case with Partner Support and request that they roll back all versions that caused the dependency to "beta," at which point you should be able to fix the problem. This will involve uninstalling all affected versions from any orgs they are installed in. It would be ideal to uninstall/delete any apps that should not be in your org, as that can cause packaging issues (as you've unfortunately discovered).

share|improve this answer

answered 2 hours ago

sfdcfoxsfdcfox

257k12201444

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Awesome, thank you for the info. What I suspect happened is when I copied all my code from my dev into the packaging org the SF connected apps dependency got somehow included. This is going to sound really dumb, but since this is a developer org I'm not able to open a case from that account. How would I go about logging a case with them for this org?
  
  – Kenji776
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Kenji776 If you're an ISV, you'd just log a case through your ISV account. If not, there's probably nothing you can do about it short of building a new package. Managed packages are not to be trifled with, they are very finicky.
  
  – sfdcfox
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'd log something through the partner portal and provide the org ID. Good luck though.
  
  – Matt Lacey♦
  1 hour ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Alright, thanks guys. I'll see about getting a case opened. This package is being developed for a client and they already have a released version that went through security review and all that so building a new package is all but off the table. Lets hope support can help fix this mess or else I'm hosed.
  
  – Kenji776
  1 hour ago
  

  
  
  
  

add a comment | 

You can't directly "undo" a dependency once you upload a "released" version that causes the dependency. What you need to do is open a case with Partner Support and request that they roll back all versions that caused the dependency to "beta," at which point you should be able to fix the problem. This will involve uninstalling all affected versions from any orgs they are installed in. It would be ideal to uninstall/delete any apps that should not be in your org, as that can cause packaging issues (as you've unfortunately discovered).

share|improve this answer

answered 2 hours ago

sfdcfoxsfdcfox

257k12201444

share|improve this answer

answered 2 hours ago

sfdcfoxsfdcfox

257k12201444

answered 2 hours ago

sfdcfoxsfdcfox

257k12201444

answered 2 hours ago

sfdcfoxsfdcfox

257k12201444

0

I was actually able to find a fix for this. I uninstalled the Salesforce Connected Apps package which removed the reference to it in all my code. I was then able to upload a new version of the package which did not have the dependency and hence no error! Thanks @sfdcfox for pointing me the right direction!

share|improve this answer

answered 35 mins ago

Kenji776Kenji776

285412

add a comment | 

0

I was actually able to find a fix for this. I uninstalled the Salesforce Connected Apps package which removed the reference to it in all my code. I was then able to upload a new version of the package which did not have the dependency and hence no error! Thanks @sfdcfox for pointing me the right direction!

share|improve this answer

answered 35 mins ago

Kenji776Kenji776

285412

add a comment | 

I was actually able to find a fix for this. I uninstalled the Salesforce Connected Apps package which removed the reference to it in all my code. I was then able to upload a new version of the package which did not have the dependency and hence no error! Thanks @sfdcfox for pointing me the right direction!

share|improve this answer

answered 35 mins ago

Kenji776Kenji776

285412

share|improve this answer

answered 35 mins ago

Kenji776Kenji776

285412

answered 35 mins ago

Kenji776Kenji776

285412

answered 35 mins ago

Kenji776Kenji776

285412