Salesforce package error error “You can't specify version for namespace sf_com_apps because this namespace...












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."










share|improve this question

























  • I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.

    – Matt Lacey
    3 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
    2 hours ago
















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."










share|improve this question

























  • I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.

    – Matt Lacey
    3 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
    2 hours ago














1












1








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."










share|improve this question
















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















share|improve this question













share|improve this question




share|improve this question








edited 3 hours ago









Matt Lacey

20.9k547120




20.9k547120










asked 3 hours ago









Kenji776Kenji776

285412




285412













  • I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.

    – Matt Lacey
    3 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
    2 hours ago



















  • I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.

    – Matt Lacey
    3 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
    2 hours ago

















I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.

– Matt Lacey
3 hours ago





I've had this in sandboxes and have always managed to remove the dependancy, never with the actual package though.

– Matt Lacey
3 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





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
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
2 hours ago










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
























  • 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
    2 hours 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
    2 hours ago











  • I'd log something through the partner portal and provide the org ID. Good luck though.

    – Matt Lacey
    2 hours 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
    2 hours ago



















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























    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


















    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















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    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
























    • 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
      2 hours 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
      2 hours ago











    • I'd log something through the partner portal and provide the org ID. Good luck though.

      – Matt Lacey
      2 hours 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
      2 hours ago
















    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
























    • 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
      2 hours 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
      2 hours ago











    • I'd log something through the partner portal and provide the org ID. Good luck though.

      – Matt Lacey
      2 hours 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
      2 hours ago














    3












    3








    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













    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












    share|improve this answer



    share|improve this answer










    answered 2 hours ago









    sfdcfoxsfdcfox

    257k12201444




    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
      2 hours 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
      2 hours ago











    • I'd log something through the partner portal and provide the org ID. Good luck though.

      – Matt Lacey
      2 hours 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
      2 hours ago



















    • 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
      2 hours 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
      2 hours ago











    • I'd log something through the partner portal and provide the org ID. Good luck though.

      – Matt Lacey
      2 hours 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
      2 hours ago

















    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
    2 hours ago





    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
    2 hours 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
    2 hours 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
    2 hours ago













    I'd log something through the partner portal and provide the org ID. Good luck though.

    – Matt Lacey
    2 hours ago





    I'd log something through the partner portal and provide the org ID. Good luck though.

    – Matt Lacey
    2 hours 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
    2 hours 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
    2 hours ago













    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




























      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


























        0












        0








        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













        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












        share|improve this answer



        share|improve this answer










        answered 1 hour ago









        Kenji776Kenji776

        285412




        285412






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Salesforce Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            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















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            TypeError: fit_transform() missing 1 required positional argument: 'X'