Mac Mojave: Disabling FinderSync extension from System Preferences doesn't actually disable extension in...











up vote
1
down vote

favorite












I see that on Mojave, disabling FinderSync extension from System Preferences doesn't actually disable the extension in Finder. The supposed-to-be-disabled extension still functions normally. I need to kill the Finder process or the actual FinderSync process to actually disable the extension in Finder. Is everyone else seeing the same behavior? If so, is this a bug or a feature? :) (I vote bug btw :)). On 10.13 and earlier it works the way you'd expect it to -- the extension is indeed immediately disabled in Finder.



Just speculating here, but are we supposed to use the 10.14 specific API showExtensionManagementInterface to do the disabling/enabling in Mojave? (https://developer.apple.com/documentation/findersync/fifindersynccontroller/3021184-showextensionmanagementinterface)



Thanks










share|improve this question






















  • I've also noticed this. Have you filed a radar? I will duplicate.
    – pkamb
    Nov 30 at 0:33










  • showExtensionManagementInterface() is used to open System Preferences to the correct pane so that the user can manually enable/disable the Extension. Nothing to do with this question, really.
    – pkamb
    Nov 30 at 0:35






  • 1




    @pkamb yes, reported bug #46207982
    – Vivek
    Dec 2 at 18:08















up vote
1
down vote

favorite












I see that on Mojave, disabling FinderSync extension from System Preferences doesn't actually disable the extension in Finder. The supposed-to-be-disabled extension still functions normally. I need to kill the Finder process or the actual FinderSync process to actually disable the extension in Finder. Is everyone else seeing the same behavior? If so, is this a bug or a feature? :) (I vote bug btw :)). On 10.13 and earlier it works the way you'd expect it to -- the extension is indeed immediately disabled in Finder.



Just speculating here, but are we supposed to use the 10.14 specific API showExtensionManagementInterface to do the disabling/enabling in Mojave? (https://developer.apple.com/documentation/findersync/fifindersynccontroller/3021184-showextensionmanagementinterface)



Thanks










share|improve this question






















  • I've also noticed this. Have you filed a radar? I will duplicate.
    – pkamb
    Nov 30 at 0:33










  • showExtensionManagementInterface() is used to open System Preferences to the correct pane so that the user can manually enable/disable the Extension. Nothing to do with this question, really.
    – pkamb
    Nov 30 at 0:35






  • 1




    @pkamb yes, reported bug #46207982
    – Vivek
    Dec 2 at 18:08













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I see that on Mojave, disabling FinderSync extension from System Preferences doesn't actually disable the extension in Finder. The supposed-to-be-disabled extension still functions normally. I need to kill the Finder process or the actual FinderSync process to actually disable the extension in Finder. Is everyone else seeing the same behavior? If so, is this a bug or a feature? :) (I vote bug btw :)). On 10.13 and earlier it works the way you'd expect it to -- the extension is indeed immediately disabled in Finder.



Just speculating here, but are we supposed to use the 10.14 specific API showExtensionManagementInterface to do the disabling/enabling in Mojave? (https://developer.apple.com/documentation/findersync/fifindersynccontroller/3021184-showextensionmanagementinterface)



Thanks










share|improve this question













I see that on Mojave, disabling FinderSync extension from System Preferences doesn't actually disable the extension in Finder. The supposed-to-be-disabled extension still functions normally. I need to kill the Finder process or the actual FinderSync process to actually disable the extension in Finder. Is everyone else seeing the same behavior? If so, is this a bug or a feature? :) (I vote bug btw :)). On 10.13 and earlier it works the way you'd expect it to -- the extension is indeed immediately disabled in Finder.



Just speculating here, but are we supposed to use the 10.14 specific API showExtensionManagementInterface to do the disabling/enabling in Mojave? (https://developer.apple.com/documentation/findersync/fifindersynccontroller/3021184-showextensionmanagementinterface)



Thanks







macos-mojave findersync






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 at 12:40









Vivek

414411




414411












  • I've also noticed this. Have you filed a radar? I will duplicate.
    – pkamb
    Nov 30 at 0:33










  • showExtensionManagementInterface() is used to open System Preferences to the correct pane so that the user can manually enable/disable the Extension. Nothing to do with this question, really.
    – pkamb
    Nov 30 at 0:35






  • 1




    @pkamb yes, reported bug #46207982
    – Vivek
    Dec 2 at 18:08


















  • I've also noticed this. Have you filed a radar? I will duplicate.
    – pkamb
    Nov 30 at 0:33










  • showExtensionManagementInterface() is used to open System Preferences to the correct pane so that the user can manually enable/disable the Extension. Nothing to do with this question, really.
    – pkamb
    Nov 30 at 0:35






  • 1




    @pkamb yes, reported bug #46207982
    – Vivek
    Dec 2 at 18:08
















I've also noticed this. Have you filed a radar? I will duplicate.
– pkamb
Nov 30 at 0:33




I've also noticed this. Have you filed a radar? I will duplicate.
– pkamb
Nov 30 at 0:33












showExtensionManagementInterface() is used to open System Preferences to the correct pane so that the user can manually enable/disable the Extension. Nothing to do with this question, really.
– pkamb
Nov 30 at 0:35




showExtensionManagementInterface() is used to open System Preferences to the correct pane so that the user can manually enable/disable the Extension. Nothing to do with this question, really.
– pkamb
Nov 30 at 0:35




1




1




@pkamb yes, reported bug #46207982
– Vivek
Dec 2 at 18:08




@pkamb yes, reported bug #46207982
– Vivek
Dec 2 at 18:08

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53393207%2fmac-mojave-disabling-findersync-extension-from-system-preferences-doesnt-actua%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


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





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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%2fstackoverflow.com%2fquestions%2f53393207%2fmac-mojave-disabling-findersync-extension-from-system-preferences-doesnt-actua%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'