site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Hi, Thanks for any help! Cheers, Josh RFCOMMClientSample/ChatClientController.m, line 160: RFCOMMServerSample/ChatServerController.m, line 187: should be: _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... I'm developing an app that makes RFCOMM connections between two unpaired Macs (running 10.5.8) and if either machine has simple pairing turned on, they both bring up a pairing request dialog when opening the connection. (The same thing happens when running the RFCOMMClientSample & RFCOMMServerSample apps from the Bluetooth developer examples*). If simple pairing is turned off (using Bluetooth Explorer) or if the connection is with an earlier system version (10.5.4), the pairing dialog doesn't appear. The connection succeeds regardless of the user's action on the pairing requests - it just adds unnecessary UI clutter and temporarily freezes the app - so I'd like to find a way to programmatically turn off simple pairing like Bluetooth Explorer does, or at least intercept the dialog. (Tried swizzling IOBluetoothDevice's requestAuthentication method but no dice). * Unrelated to the above, both the RFCOMMClientSample & RFCOMMServerSample examples from Xcode 3.1 have a bug that prevents remote messages from being displayed, due to a missing parameter: [[NSString alloc] initWithBytes:[dataObject bytes] length:[dataObject length]] [[NSString alloc] initWithBytes:[dataObject bytes] length:[dataObject length] encoding: NSUTF8StringEncoding] This email sent to site_archiver@lists.apple.com