I'm using a Twitter Desktop client named NightOwl with older version of OS X (can't upgrade). You upload pictures to Twitter from NightOwl (aka YoruFukurou) by first setting your account with one of image hosting and sharing services, in my case from Mobypicture service and then choosing its name on the app's "Services" pane. The upload as I understand it is done through Mobypicture with NightOwl functioning as the front-end by providing UI through which you select your image from the computer's hard drive. All went fine until it refused to do that today with the error "Failed to upload" raised. I went usual routine path of troubleshooting (incl. permissions repair) which I skip for the sake of saving your time. Nothing helped.
I then opened Console and noticed these messages:
Notice all the lines containing deny file-ioctl. They point to the files - pictures uploaded by choosing "Upload image" and screenshots done using "Upload screenshot" feature of the app - that the app failed to upload. Copies of the images that were not screen-captures for some reason ended up being tucked away in /private/var/folders/3q/k7smvfkn33z49q4xdy_lfv7h0000gn/T/com.YoruFukurouProject.YoruFukurou folder.
I looked through some explanations of what ioctl typically refers to (device drivers or smth) but still can't fathom why all of sudden sandbox would reject uploading my files from Hard Drive using 3rd party hosting service? NightOwl is sandboxed app from MAS but nothing could imply that it is a cause because up until several days ago the function was working as designed. Also it strange to see the line with NightOwl and Waterfox (my default browser) put together.
I can share the image from Mobypicture. It will delay showing up in NightOwl by hours. Also I noticed the service doesn't use secure connection if that helps.
The developer of the app is not responsive at all even though his contact info and the website (a minuscule page-like web-snippet in fact) are available in the app's room in MAS.
Could you, more experienced with coding and how OS X processes work, at least shed some light to what might be behind the picture? Can it be that my OS X is too old or there's smth more to it?
How could "sandboxd" be told not to interfere?
I then opened Console and noticed these messages:
HTML:
29.08.18 16:23:13,283 sandboxd ([25667]) screencapture(25667) deny file-write-data /
29.08.18 16:23:17,062 sandboxd ([25671]) file(25671) deny file-ioctl /private/var/folders/3q/k7smvfkn33z49q4xdy_lfv7h0000gn/T/com.YoruFukurouProject.YoruFukurou/screenshot_39CE855C-1309-4D0C-BD06-14D370C541CE.png
29.08.18 16:26:49,286 sandboxd ([25733]) screencapture(25733) deny file-write-data /
29.08.18 16:27:47,291 sandboxd ([25757]) screencapture(25757) deny file-write-data /
29.08.18 16:28:09,005 sandboxd ([25764]) screencapture(25764) deny file-write-data /
29.08.18 16:28:11,675 sandboxd ([25768]) file(25768) deny file-ioctl /private/var/folders/3q/k7smvfkn33z49q4xdy_lfv7h0000gn/T/com.YoruFukurouProject.YoruFukurou/screenshot_2CECC05B-B7DD-42C6-BDA9-DEE61048924B.png
29.08.18 16:53:25,451 sandboxd ([26206]) file(26206) deny file-ioctl /Users/***/Pictures/Ilja2.jpg
29.08.18 17:08:03,713 sandboxd ([25796]) Night Owl(25796) deny file-write-data /Applications/OS X functionality enhancing software/Waterfox.app
29.08.18 17:15:26,380 sandboxd ([26581]) file(26581) deny file-ioctl /Users/***/Desktop/Unavlb.png
Notice all the lines containing deny file-ioctl. They point to the files - pictures uploaded by choosing "Upload image" and screenshots done using "Upload screenshot" feature of the app - that the app failed to upload. Copies of the images that were not screen-captures for some reason ended up being tucked away in /private/var/folders/3q/k7smvfkn33z49q4xdy_lfv7h0000gn/T/com.YoruFukurouProject.YoruFukurou folder.
I looked through some explanations of what ioctl typically refers to (device drivers or smth) but still can't fathom why all of sudden sandbox would reject uploading my files from Hard Drive using 3rd party hosting service? NightOwl is sandboxed app from MAS but nothing could imply that it is a cause because up until several days ago the function was working as designed. Also it strange to see the line with NightOwl and Waterfox (my default browser) put together.
I can share the image from Mobypicture. It will delay showing up in NightOwl by hours. Also I noticed the service doesn't use secure connection if that helps.
The developer of the app is not responsive at all even though his contact info and the website (a minuscule page-like web-snippet in fact) are available in the app's room in MAS.
Could you, more experienced with coding and how OS X processes work, at least shed some light to what might be behind the picture? Can it be that my OS X is too old or there's smth more to it?
How could "sandboxd" be told not to interfere?
Last edited: