gatt client: Fix SIGABRT 01/159901/2 submit/tizen_3.0/20171207.001107
authorAnupam Roy <anupam.r@samsung.com>
Mon, 13 Nov 2017 12:35:02 +0000 (18:05 +0530)
committerAnupam Roy <anupam.r@samsung.com>
Mon, 13 Nov 2017 13:04:34 +0000 (18:34 +0530)
JIRA Issue: http://suprem.sec.samsung.net/jira/browse/TSAM-14037

[Problem] Application terminates when GATT descriptor
          'WriteValue' API fails.
[Cause] In case of error in BlueZ DBUS API 'WriteValue', NULL
        is received in g_dbus_connection_call_finish() in gatt
        client. So, instead of returning after chekcing
        error value, code was trying to unref NULL value causing
        application to terminate abnormally.
[Measure] Return from GATT write descriptor callback, in case of error.
[Checking Method] Perform GATT desc 'WriteValue' using bt_unit_test.

Change-Id: I9fd230e091e5a16618c8d36ebbe94bafc768ef92
Signed-off-by: Anupam Roy <anupam.r@samsung.com>

No differences found