0

I have an app that uses IOBluetooth to register itself as a Bluetooth service and set itself to auto-start when receiving an incoming RFCOMM connection.

It was working on OS X Lion.

However on Mavericks, the app doesn't start, and if I open console, I see this:

sandboxd[314]: ([83]) blued(83) deny file-read-metadata /Applications/MyBluetoothApp.app

It looks like sandboxd is blocking me. Why? Shouldn't the IOBluetooth API's take care of this? How can I prevent this from happening?

T.Coutlakis
  • 2,436
  • 1
  • 19
  • 19
  • Maybe an entitlement issue? https://developer.apple.com/library/mac/documentation/Miscellaneous/Reference/EntitlementKeyReference/Chapters/EnablingAppSandbox.html#//apple_ref/doc/uid/TP40011195-CH4-SW11 – bbum Oct 27 '13 at 19:06
  • Maybe! Thanks I am looking now... – T.Coutlakis Oct 27 '13 at 23:18
  • 1
    App Sandbox was introduced in OS X v10.7 Lion, and my app was working fine then. So is that really the issue? Anyway, the console message seems to suggest that blued has "entitlement" issues, as it is the one supposed to launch my app (my app is not even running when that message is logged). – T.Coutlakis Oct 28 '13 at 01:05
  • The details of sandboxing change from release to release. Entitlements can control more than just your app's behavior, but also interaction between the system and your app. It was a guess, hence presented as a comment, because I'm not sure what the real problem might be. – bbum Oct 28 '13 at 01:28
  • Just confirmed that my app isn't using the sandbox. – T.Coutlakis Oct 28 '13 at 18:45
  • Thus leaving me with not a clue! Sorry. – bbum Oct 28 '13 at 22:12

0 Answers0