Fix the malfunction of gatt write request 92/232492/1 submit/tizen/20200506.041322
authorinjun.yang <injun.yang@samsung.com>
Wed, 29 Apr 2020 10:46:12 +0000 (19:46 +0900)
committerWootak Jung <wootak.jung@samsung.com>
Wed, 6 May 2020 02:12:17 +0000 (11:12 +0900)
commit11e2c532762e017b176c353eea3da3ca75ad60b0
treeb9e6d186a88c47314af4ccbecfacfa145892dff2
parenta5050242c77bf67df8dcba219592bc7cd36191f2
Fix the malfunction of gatt write request

[Model] All
[BinType] AP
[Customer] OPEN

[Issue#] P200428-04425
[Request] Internal
[Occurrence Version] N/A

[Problem] Some application call bt_gatt_client_write_value() repeately. (Write req)
 If gatt client app call API before callback invoked,
 inprogress error is not returned.
[Cause & Measure] ATT is sequential transaction protocol. So return inprogress error
 before write completed callback invoked.
[Checking Method] n/a

[Team] Convergence BT
[Developer] Injun Yang
[Solution company] Samsung
[Change Type] Specification change

Change-Id: I76eb97e124a739990d3210c3f3c3fa7354b605f1
Signed-off-by: Wootak Jung <wootak.jung@samsung.com>
src/bluetooth-gatt.c