Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Didn't respond to ATT #126

Open
yueyuzhao opened this issue Oct 6, 2023 · 0 comments · May be fixed by #127
Open

Didn't respond to ATT #126

yueyuzhao opened this issue Oct 6, 2023 · 0 comments · May be fixed by #127

Comments

@yueyuzhao
Copy link

According to the CoreBluetooth document,

peripheralManager(_:didReceiveRead:)

When you receive this callback, call the respond(to:withResult:) method of the CBPeripheralManager class exactly once to respond to the read request.

source: https://developer.apple.com/documentation/corebluetooth/cbperipheralmanagerdelegate/1393257-peripheralmanager#discussion

peripheralManager(_:didReceiveWrite:)

In the same way that you respond to a read request, each time you receive this callback, call the respond(to:withResult:) method of the CBPeripheralManager class exactly once. If the requests parameter contains multiple requests, treat them as you would a single request—if you can’t fulfill an individual request, you shouldn’t fulfill any of them. Instead, call the respond(to:withResult:) method immediately, and provide a result that indicates the cause of the failure.

source: https://developer.apple.com/documentation/corebluetooth/cbperipheralmanagerdelegate/1393315-peripheralmanager#discussion

@yueyuzhao yueyuzhao linked a pull request Oct 6, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant