Closed buckleyc closed 4 years ago
The same here! Tried to run it from terminal:
~ % /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
2020-04-13 00:48:00.262 BlockBlock[2397:52166] Sentry Started -- Version: 3.12.4
INFO : KSCrash.m (339): -[KSCrash sendAllReportsWithCompletion:]: Sending 0 crash reports
~ % sudo /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
Password:
2020-04-13 00:48:20.447 BlockBlock[2400:52274] Sentry Started -- Version: 3.12.4
INFO : KSCrash.m (339): -[KSCrash sendAllReportsWithCompletion:]: Sending 0 crash reports
~ % /Library/Objective-See/BlockBlock/BlockBlock.app
zsh: permission denied: /Library/Objective-See/BlockBlock/BlockBlock.app
~ % sudo /Library/Objective-See/BlockBlock/BlockBlock.app
sudo: /Library/Objective-See/BlockBlock/BlockBlock.app: command not found
Thanks for the bug report! Can you see if there is any more info in the system log file?
Either run (from the terminal): log show | grep BlockBlock or Open Console.app, filter on BlockBlock, and then re-run the Installer?
Any message with "ERROR" or "FDA" would likely provide more details on the issue!
Thanks again!
Hi!
thanks for prompt reply. Full log output for current session is attached. The most useful part of it is probably 'ERROR: full disk access: denied' (see below). But it's permitted...
[image: image.png]
Cheers and regards, Anton
2020-04-13 00:40:52.636245+0300 0xc2d0 Default 0x0 2358 0 sudo: aak : TTY=ttys000 ; PWD=/usr/local/etc/stunnel ; USER=root ; COMMAND=/Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock 2020-04-13 00:40:52.650556+0300 0xc2d3 Default 0x0 2359 0 BlockBlock: BlockBlock.app(2359): launch daemon started with (
"/Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock" 2020-04-13 00:40:52.659727+0300 0xc2d3 Default 0x0 2359 0 BlockBlock: (Sentry) Sentry Started -- Version: 3.12.4 2020-04-13 00:40:52.664222+0300 0xc2d3 Default 0x0 2359 0 BlockBlock: BlockBlock.app(2359): performing full disk access check... 2020-04-13 00:40:52.664284+0300 0xc2d3 Default 0x0 2359 0 BlockBlock: BlockBlock.app(2359): result: -1 2020-04-13 00:40:52.664291+0300 0xc2d3 Default 0x0 2359 0 BlockBlock: BlockBlock.app(2359) ERROR: full disk access: denied 2020-04-13 00:48:00.194526+0300 0xcbc6 Activity 0x13a50 2397 0 BlockBlock: (libsystem_info.dylib) Retrieve User by ID 2020-04-13 00:48:00.196487+0300 0xcbc6 Default 0x0 2397 0 BlockBlock: BlockBlock.app(2397): launch daemon started with (
"/Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock" 2020-04-13 00:48:00.215900+0300 0xcbc6 Default 0x0 2397 0 BlockBlock: (Sentry) Sentry Started -- Version: 3.12.4 2020-04-13 00:48:00.221216+0300 0xcbc6 Default 0x0 2397 0 BlockBlock: BlockBlock.app(2397) ERROR: launch daemon must be run as root 2020-04-13 00:48:00.221227+0300 0xcbc6 Default 0x0 2397 0 BlockBlock: BlockBlock.app(2397): launch daemon exiting 2020-04-13 00:48:00.221236+0300 0xcbc6 Default 0x0 2397 0 BlockBlock: BlockBlock.app(2397): logging ending 2020-04-13 00:48:20.378925+0300 0xcc04 Default 0x0 2399 0 sudo: aak : TTY=ttys000 ; PWD=/Users/aak ; USER=root ; COMMAND=/Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock 2020-04-13 00:48:20.391215+0300 0xcc32 Default 0x0 2400 0 BlockBlock: BlockBlock.app(2400): launch daemon started with (
"/Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock" 2020-04-13 00:48:20.400687+0300 0xcc32 Default 0x0 2400 0 BlockBlock: (Sentry) Sentry Started -- Version: 3.12.4 2020-04-13 00:48:20.405785+0300 0xcc32 Default 0x0 2400 0 BlockBlock: BlockBlock.app(2400): performing full disk access check... 2020-04-13 00:48:20.405848+0300 0xcc32 Default 0x0 2400 0 BlockBlock: BlockBlock.app(2400): result: -1 2020-04-13 00:48:20.405855+0300 0xcc32 Default 0x0 2400 0 BlockBlock: BlockBlock.app(2400) ERROR: full disk access: denied
On Mon, Apr 13, 2020 at 1:19 AM Objective-See notifications@github.com wrote:
Thanks for the bug report!
- Can you see if there is any more info in the system log file?
Either run (from the terminal): log show | grep BlockBlock or Open Console.app, filter on BlockBlock, and then re-run the Installer? [image: image] https://user-images.githubusercontent.com/11327812/79081283-ace88380-7cb7-11ea-903e-3805ee9e9cf5.png
Any message with "ERROR" or "FDA" would likely provide more details on the issue!
Thanks again!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/objective-see/BlockBlock/issues/1#issuecomment-612684712, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB2XDZ4DCNANUZBL5VXGT5TRMI5ANANCNFSM4MGSBLSQ .
2020-04-12 23:51:31.320599+0300 0x187d Activity 0x4980 732 0 BlockBlock: (CoreFoundation) Loading Preferences From User CFPrefsD
2020-04-12 23:51:33.745546+0300 0x187d Activity 0x4981 732 0 BlockBlock: (AppKit) perform action for menu item
2020-04-12 23:51:33.747028+0300 0x187d Activity 0x4982 732 0 BlockBlock: (AppKit) sendAction:
2020-04-12 23:51:33.802083+0300 0x187d Default 0x4982 732 0 BlockBlock: (libDiagnosticMessagesClient.dylib) MessageTracer: Falling back to default whitelist
2020-04-12 23:51:33.802309+0300 0x187d Default 0x4982 732 0 BlockBlock: (HIServices) [com.apple.processmanager:front-35286506] SetFrontProcess: asn=0x0-0x3d03d options=1
2020-04-12 23:51:33.802994+0300 0x6fe5 Default 0x0 732 0 BlockBlock: (CoreAnalytics) [com.apple.CoreAnalytics:client] Received configuration update from daemon (initial)
2020-04-12 23:51:33.949525+0300 0x7ba8 Default 0x0 315 0 hidd: (IOKit) [com.apple.iohid:default] Connection added: IOHIDEventSystemConnection uuid:072EF3A7-95FD-495C-8A59-F5C735A288FB pid:732 process:BlockBlock type:Passive entitlements:0x0 caller:HIToolbox: _GetIOHIDEventSystemClient_blockinvoke + 26 attributes:(null) state:0x0 events:0 mask:0x0
2020-04-12 23:51:34.270810+0300 0x78e4 Default 0x0 315 0 hidd: (IOKit) [com.apple.iohid:default] Connection added: IOHIDEventSystemConnection uuid:AB2F9294-C9A6-40E8-B88F-761194FB8F54 pid:732 process:BlockBlock type:Passive entitlements:0x0 caller:HIServices: GetIOHIDEventSystemClient_block_invoke + 26 attributes:(null) state:0x0 events:0 mask:0x0
2020-04-12 23:51:34.964165+0300 0x187d Activity 0x4983 732 0 BlockBlock: (CoreFoundation) Loading Preferences From User CFPrefsD
2020-04-12 23:51:35.012483+0300 0x7bb0 Default 0x0 732 0 BlockBlock: (AggregateDictionary) AggregateDictionary is not supported on this platform
2020-04-12 23:51:37.158569+0300 0x187d Activity 0x4984 732 0 BlockBlock: (CoreFoundation) Loading Preferences From User CFPrefsD
2020-04-12 23:51:37.159029+0300 0x187d Activity 0x4985 732 0 BlockBlock: (CoreFoundation) Loading Preferences From User CFPrefsD
2020-04-12 23:51:37.245682+0300 0x187d Activity 0x4986 732 0 BlockBlock: (AppKit) trackMouse send action on mouseUp
2020-04-12 23:51:37.245687+0300 0x187d Activity 0x4987 732 0 BlockBlock: (AppKit) sendActionFrom:
2020-04-12 23:51:37.245733+0300 0x187d Activity 0x4988 732 0 BlockBlock: (AppKit) sendAction:
2020-04-12 23:51:38.306659+0300 0x7bb0 Default 0x4988 732 0 BlockBlock: (CFNetwork) [com.apple.CFNetwork:ATS] Task
I just came to report this same issue. I have granted both /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
and /Library/Objective-See/BlockBlock/BlockBlock.app
full disk access.
I have re-run the installer and got the same error message as in the first post in this bug report.
When I manually run /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
it gives this for output:
2020-04-12 20:46:55.154 BlockBlock[63356:8489585] Sentry Started -- Version: 3.12.4
INFO : KSCrash.m (339): -[KSCrash sendAllReportsWithCompletion:]: Sending 0 crash reports
And then nothing.
By using LaunchControl I was able to edit /Library/LaunchDaemons/com.objective-see.blockblock.plist
to use its fdautil
tool (which is basically a helper tool specific to LaunchControl that has Full Disk Access).
Once I did that then the LaunchDaemon included this:
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/fdautil</string>
<string>exec</string>
<string>/Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock</string>
</array>
After that change, BlockBlock ran fine. I see
/Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
running as root and
/Applications/BlockBlock Helper.app/Contents/MacOS/BlockBlock Helper
running as my user.
So it's working for me, but only because I had LaunchControl.
p.s. - edited to add -- I noticed that the installer was running under "App Translocation" -- I guess because I ran it from ~/Downloads/ rather than /Applications/ ? Anyway, I manually moved the installer to /Applications/ and then uninstalled and re-installed BlockBlock 1.0 but it did not change the end result.
Maybe this is a potentially dumb question, but can I ask why you aren't using a regular Mac .pkg
to install this?
I assume there's a reason besides being able to pop-up the Patreon prompt.
Thanks for additional feedback!
Some additional suggestions (if you wouldn't mind helping track this down).
...does the following still show up in the log? ERROR: full disk access: denied
$ sudo /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
Thanks!
I'm happy to do whatever I can to help debug the issue, I just hope that I'm understanding what you're asking, so I'll try to be explicit about what I did.
I ran the command sudo /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
while also running command log show | grep BlockBlock
and it produced the output in the attached file.
(Note: I use command log
instead of log
because zsh
has a built-in log
command that I thinks I want to use otherwise. command log
tells zsh
to use /usr/bin/log
not the zsh-built-in. Also, I don't think it matters, but I use iTerm instead of Terminal.app, but iTerm has FDA also.)
Running sudo launchctl load /Library/LaunchDaemons/com.objective-see.blockblock.plist
while running command log show | grep BlockBlock
did not show any errors, but also did not result in any BlockBlock
process showing up when I do pgrep -fil blockblock
I hope that's helpful. Let me know if there's anything else I can try.
Thanks @tjluoma!
...can you re-run with the log stream
command (as log show
will (only?) show older messages - so maybe not have the 'current' BlockBlock message)
OK, so I started command log stream | grep BlockBlock
and then ran sudo /Library/Objective-See/BlockBlock/BlockBlock.app/Contents/MacOS/BlockBlock
The sudo
command created this output:
2020-04-12 22:15:25.386 BlockBlock[6043:8705510] Sentry Started -- Version: 3.12.4
INFO : KSCrash.m (339): -[KSCrash sendAllReportsWithCompletion:]: Sending 0 crash reports
and continued to run until I did Control+C.
The command log
output is here:
Oh, I should also add, that although BlockBlock was running during this time, it did not show me any GUI alerts when I moved two new .plists into ~/Library/LaunchAgents/ and loaded them. So it does not seem to be working properly for me for some reason, even when it is running. Unless I'm missing something.
Just to mention I apparently have the same issue.
Still digging into this (as frustratingly I haven't been able to replicated it on my dev box or VM).
Two suggestions:
Some users have stated a reboot fixed it!
Also, I've just posted a new version that has some other fixes and (in the daemon) checks for FDA in another way. Not sure if it fixes it, but worth a try: BlockBlock_BETA.zip
....also @tjluoma this new version should fix the issue where the plists
weren't triggering an alert!
Thanks for your feedback and patience!
2. Not sure if it fixes it, but worth a try: BlockBlock_BETA.zip
This installer manages to add the BlockBlock app into the Full Disk Access list. However the Block Block helper still warns me that the Daemon is not running.
Reboot fixed it for me. I am using macOS 10.15.4(19E287)
Prior to that "launchctl load" reported that the plist was loaded but it wouldn't start. Could the old plist have still been loaded?
New version did not fix it, but a reboot seems to have done it.
Same here with macOS 10.15.4 (German): after updating from 0.9.9.4 same situation as the thread opener. After rebooting it worked fine.
Works after a reboot. I had latest 0.9 installed previously.
I, too, had the same issue as initially described. I have a couple of other items that are relevant that have not yet been posted. First, note that I had an earlier version (?) installed. I performed the Uninstall from within BlockBlock before I installed the 1.0.0 version.
After the failed install (from this initial post), I could not use BlockBlock to Uninstall, as it would not launch. So:
Surprise: There was something still trying to run, despite my attempted uninstall. Conclusion: Something about the install doesn't leave around the normal breadcrumbs that CleanMyMac X (normally) uses to find all the shmutz required to uninstall something.
Here's what Log / Grep found:
Space-Catalyst:~ batsonjay$ log show | grep BlockBlock 2020-04-02 11:19:41.845303-0400 0x1507 Default 0x0 548 7 BlockBlock: (SkyLight) [com.apple.SkyLight:default] Set a breakpoint at SLSLogBreak to catch errors/faults as they are logged. 2020-04-02 11:19:41.845315-0400 0x1507 Error 0x0 548 7 BlockBlock: (SkyLight) [com.apple.SkyLight:default] enable_updates_common timed out waiting for updates to reenable 2020-04-02 11:25:38.669377-0400 0x1507 Error 0x0 548 7 BlockBlock: (SkyLight) [com.apple.SkyLight:default] enable_updates_common timed out waiting for updates to reenable 2020-04-05 21:21:04.069385-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-05 21:21:04.069562-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-05 21:21:04.119176-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 2), (SLS: 1) 2020-04-05 21:21:04.119329-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-05 21:21:04.129625-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-06 07:00:55.897414-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-06 07:00:55.897423-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-06 07:00:55.897945-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 1), (SLS: 0) 2020-04-06 07:00:55.897965-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-06 07:00:55.899194-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-06 14:00:57.682347-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-06 14:01:04.895141-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning
(This then repeats starting at APpleInterfaceThemeChangedNotification, repeating about every couple of minutes.)
Next: I simply deleted /Library/Objective-See/BlockBlock Reboot Re-run log SURPRISE: It's still catching those BlockBlock errors. BlockBlock turns out to be surprisingly hard to get rid of once you've had a failed install.
So, I re-ran the 1.0.0 install ... and guess what? I get an option to Uninstall BlockBlock. I took it. Reboot Re-run log NO SUPRISE: It's till catching those same BlockBlock errors. BlockBlock seems surprisingly hard to uninstall - even if asked to do so....
Space-Catalyst:~ batsonjay$ log show | grep BlockBlock 2020-04-02 11:19:41.845303-0400 0x1507 Default 0x0 548 7 BlockBlock: (SkyLight) [com.apple.SkyLight:default] Set a breakpoint at SLSLogBreak to catch errors/faults as they are logged. 2020-04-02 11:19:41.845315-0400 0x1507 Error 0x0 548 7 BlockBlock: (SkyLight) [com.apple.SkyLight:default] enable_updates_common timed out waiting for updates to reenable 2020-04-02 11:25:38.669377-0400 0x1507 Error 0x0 548 7 BlockBlock: (SkyLight) [com.apple.SkyLight:default] enable_updates_common timed out waiting for updates to reenable 2020-04-05 21:21:04.069385-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-05 21:21:04.069562-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-05 21:21:04.119176-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 2), (SLS: 1) 2020-04-05 21:21:04.119329-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-05 21:21:04.129625-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-06 07:00:55.897414-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-06 07:00:55.897423-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-06 07:00:55.897945-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 1), (SLS: 0) 2020-04-06 07:00:55.897965-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-06 07:00:55.899194-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-06 14:00:57.682347-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-06 14:01:04.895141-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-06 20:19:18.761389-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-06 20:19:18.761409-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-06 20:19:18.766605-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 2), (SLS: 1) 2020-04-06 20:19:18.766644-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-06 20:19:18.768101-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-07 06:59:06.346186-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-07 06:59:06.346203-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-07 06:59:06.346677-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-07 06:59:06.346686-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-07 06:59:06.347800-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 1), (SLS: 0) 2020-04-07 06:59:06.347826-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-07 06:59:06.348381-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 1), (SLS: 0) 2020-04-07 06:59:06.348402-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-07 06:59:06.362982-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-07 08:01:40.387935-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 08:01:44.979282-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 10:29:30.892267-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 10:29:36.435046-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 11:01:45.072335-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 11:01:50.809054-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 14:32:48.631174-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 14:32:54.375776-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 14:32:54.429118-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) Warning: Window move completed without beginning 2020-04-07 18:49:14.086769-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-07 20:43:46.155893-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-07 20:43:46.155911-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-07 20:43:46.156121-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 2), (SLS: 1) 2020-04-07 20:43:46.156203-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] AppleInterfaceThemeChangedNotification 2020-04-07 20:43:46.156213-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] System appearance change 2020-04-07 20:43:46.156282-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-07 20:43:46.156536-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Current system appearance, (HLTB: 2), (SLS: 1) 2020-04-07 20:43:46.156583-0400 0x350 Default 0x0 134 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] Invalidate NSApp effectiveAppearance 2020-04-07 20:43:48.954692-0400 0x1507 Default 0x0 548 0 BlockBlock: (AppKit) [com.apple.AppKit:Appearance] NSApp cache appearance: 2020-04-07 20:43:52.625719-0400 0x1507 Error 0x0 548 7 BlockBlock: (SkyLight) [com.apple.SkyLight:default] enable_updates_common timed out waiting for updates to reenable
And so on ad-infinitum.
So, I'd like help ACTUALLY getting a clean uninstall. Can I ask where all the vestiges of things are so that I can make sure I'm starting with a clean slate? (And, so in the future, I know how to really uninstall.)
Then I'll likely wait a day or two until you re-release another candidate.
Update 14 April 2020 9:40am I noted the new build you included in this thread. Downloaded, installed. Appears to have installed correctly. BlockBlock is listed in the FDA list, and is enabled there. Have not tried an uninstall, but will leave that alone for now, since I need to move on.
Thanks for always making amazing software. I'm a Patreon supporter; I need to pay more, though.
Downloaded v1.0.0 beta. Installed. BlockBlock did not get added to 'Full Disk Access' (fda) by default, so /Library/Objective-See/BlockBlock/BlockBlock.app was added via "+". Tried launching multiple times, but will not execute. "BlockBlock's launch daemon not active!" The following image shows the error, as well as the setting showing it has full disk access. Have not rebooted yet (as I have running tasks; will try later.)
Update: After a restart/reboot, this is working fine, and launched properly at login. I am not closing this yet, as others are reporting the same issue, so there is definitely an issue during installation.
Fixed by a reboot for me too
Hi, same experience for me. Reboot fixed it. As far as I know, already running processes don't get full disk access when a user grants it in system preferences, but the process needs to restart after that. That would explain why the reboot helped.
(At least, when I recently updated KnockKnock and granted Full Disk Access, System Preferences showed a popup telling me to terminate and restart the app for it to get full disk access.)
BlockBlock has been downgraded to ver. 0.9.9.4? Is 1.0.0 coming back soon?
Also had this issue. Reboot fixed it for me. BlockBlock working as expected after reboot.
Good news I've finally been able to replicate this issue!
As the image shows, BlockBlock has been given Full Disk Access, and this can be confirmed by dumping the TCC.db.
But when the installer then kicks it off, macOS does not grant it FDA 😠
The issue appears that Apple/TCC gets 'confused' when an older version of BlockBlock was installed, even though the installer fully removes said old version. I believe a reboot gets macOS/TCC back to a good state (it does a new check and picks up the new version).
After talking to a few Apple folks, they suggested filing a radar with Apple for a fix. Also currently working to figure out a solution for BlockBlock (to work around this issue)
Thanks for your patience!
I was trying to read up more about how TCC is implemented, but didn't find anything in useful in 10 minutes of reading (I'm not an expert in this). If it's a process, could the installer just request to restart it, or is it implemented in the kernel?
Believe I've found a work around for Apple's TCCd
caching issue
tccd
(@jguerin 👍)...then once user has granted BlockBlock Full Disk Access via the System Preferences UI, this seems to now get propagated to BlockBlock! (no reboot required)
If ya'll want to give the latest beta a whirl I'd be stoked: https://bitbucket.org/objective-see/deploy/downloads/BlockBlock_BETA.zip
Would you rather us try to do a full uninstall, and try again? Or, just re-install over what we have?
If full uninstall, see my posting above that the "uninstall" from within the app didn't seem to fully uninstall. Can you confirm what way we can be sure to fully uninstall? (Or, maybe the thing you're testing is a re-install over an existing installation of a prior version - which maybe we should also test from a fresh uninstall?)
@objective-see confirmed that upgrade from v0.8 to 1.0.0 BETA with the fixed build addresses this issue for me.
Would you rather us try to do a full uninstall, and try again? Or, just re-install over what we have?
If full uninstall, see my posting above that the "uninstall" from within the app didn't seem to fully uninstall. Can you confirm what way we can be sure to fully uninstall? (Or, maybe the thing you're testing is a re-install over an existing installation of a prior version - which maybe we should also test from a fresh uninstall?)
@batsonjay any of those scenarios would be good to test!
re: the old version still hanging around, I added an explicit command in the uninstall logic to also unregister the (old) application during the uninstall process. Should tell macOS its really gone now!
re: the log messages, log show
will also show older log messages (from before) too. If you run log stream | grep -i blockblock
after any uninstall, hopefully nothing shows up now! 😅
I also can confirm that the new version worked for me on a second iMac. The update from 0.9.9.4 to 0.9.9.9 (?) ran as expected and without the need for a reboot.
fixes appear to well, fix this issue 🥇
Downloaded v1.0.0 beta. Installed. BlockBlock did not get added to 'Full Disk Access' (fda) by default, so /Library/Objective-See/BlockBlock/BlockBlock.app was added via "+". Tried launching multiple times, but will not execute. "BlockBlock's launch daemon not active!" The following image shows the error, as well as the setting showing it has full disk access. Have not rebooted yet (as I have running tasks; will try later.)