User Profile

Calling the Bluetooth GetMessage function for a message that was sent via Bluetooth, the returned BMessage contains an incorrect folder path to the message. The Event Report returns the correct folder path when the message is successfully sent. Scenario: Connect to Bluetooth MAP services (MNS and MAS). Call Bluetooth "PushMessage" function. Get 'Name Header' for the Message Handle. MAP-Event-Report received with Type of SendingSuccess and Folder equal to "telecom/msg/sent". Use "SetFolder" to navigate to Sent folder. Call "GetMessage" with the Message Handle (the handle is the same for both the event report and PushMessage function). The BMessage response has a folder of "telecom/msg/inbox" BMessage: BEGIN:BMSG VERSION:1.0 STATUS:UNREAD TYPE:SMS_GSM FOLDER:telecom/msg/inbox NOTIFICATION:1 BEGIN:VCARD VERSION:2.1 FN;CHARSET=UTF-8:[Contact] N;CHARSET=UTF-8:[Contact] TEL:3: END:VCARD BEGIN:BENV BEGIN:VCARD VERSION:2.1 FN;CHARSET=UTF-8:[Contact] N;CHARSET=UTF-8:[Contact] TEL:[Phone Number] END:VCARD BEGIN:BBODY CHARSET:UTF-8 LANGUAGE:UNKNOWN LENGTH:[Some Length] BEGIN:MSG iOS is the worst. END:MSG END:BBODY END:BENV END:BMSG Set Folder to telecom: 85-00-20-02-00-01-00-13-00-74-00-65-00-6C-00-65-00-63-00-6F-00-6D-00-00-4C-00-03-CB-08-60-59-D0 Set Folder to msg: 85-00-18-02-00-01-00-0B-00-6D-00-73-00-67-00-00-4C-00-03-CB-08-60-59-D0 Setting Folder to sent: 85-00-1A-02-00-01-00-0D-00-73-00-65-00-6E-00-74-00-00-4C-00-03-CB-08-60-59-D0 Calling GetMessage function: 83-00-44-01-00-23-00-44-00-33-00-42-00-43-00-34-00-45-00-39-00-31-00-30-00-35-00-41-00-41-00-34-00-43-00-32-00-00-42-00-10-78-2D-62-74-2F-6D-65-73-73-61-67-65-00-4C-00-09-14-01-01-0A-01-00-CB-08-60-59-D0 Section 3.1.4 of the Bluetooth Specification states: "telecom/msg/sent: This folder shall contain messages that were successfully sent to the network by the MSE, at least during the period of the current MAP session. In particular these messages have been queued in the 'Outbox' folder before sending and are shifted by the MSE to this folder after transmission." Apple is also nice enough to not include any additional contacts when the text message is part of a group text. This has been made unnecessarily difficult for developers to use and what's worse, it seems intentional.

After updating a device to iOS 16 beta 1, I've noticed some changes to how Bluetooth profiles behave for certain functions. Specific examples include: Message Access Profile -> The SetMessageStatus function returns "OBEX_BAD_REQUEST" where it didn't before 02-00-4E-01-00-23-00-42-00-36-00-42-00-38-00-42-00-37-00-30-00-37-00-42-00-39-00-41-00-38-00-34-00-33-00-45-00-00-42-00-16-78-2D-62-74-2F-6D-65-73-73-61-67-65-53-74-61-74-75-73-00-49-00-04-30-4C-00-09-17-01-00-18-01-01-CB-08-60-5E-20 Message Access Profile -> Getting Message Listings from the sent folder...previously I was able to retrieve messages here but am no longer able to. It would be nice if the details of any changes were noted so appropriate updates can be made. Would also be nice if Apple finally moved off of version 1.2 or whatever so I can get Conversation Listings/Conversation ID from the device. We can dream, can't we? Thanks, -Drew

I'm connecting to an iPhone 12 via Bluetooth for access to PBAP, HFP, and MAP for sending, receiving, and listening to messages/calls. Note that this is not via any kind of custom hardware but rather through a PC. When I try to run basic commands like GetMessagesListing, it always comes back empty. I can hook some events, so I at least get something, but nothing compared to other platforms. That said, is there any documentation that describes what is supported for each Bluetooth profile? I've searched through the documentation for Core Bluetooth but wasn't able to find answers to that specific question. From what I can gather, this is something that Apple doesn't seem to support as opposed to me doing it wrong. Any help is appreciated, -Dew