[NFC] Fix for passing wrong values to APDU response

Issue: http://suprem.sec.samsung.net/jira/browse/XWALK-1747

Bug: Wrong type of data in array.

Verification: NFC auto tct passrate 100% (emulator wearable)

Change-Id: I5824e51ce677d6c1c7de006ad10b509b84f00a6a
Signed-off-by: Pawel Kaczmarczyk <p.kaczmarczy@partner.samsung.com>

diff --git a/src/nfc/nfc_api.js b/src/nfc/nfc_api.js
index 8aa8b58da0b0a03f9df8dbc8fdbd23c8d8750aa0..6c3f19bcb09b9165c0fd6a5deda6388e7eded89d 100644 (file)
--- a/src/nfc/nfc_api.js
+++ b/src/nfc/nfc_api.js
@@ -692,7 +692,7 @@ NFCAdapter.prototype.removeHCEEventListener = function() {
 
 NFCAdapter.prototype.sendHostAPDUResponse = function(apdu, successCallback, errorCallback) {
   var args = validator_.validateArgs(arguments, [
-    {name: 'apdu', type: types_.ARRAY, values: types_.BYTE},
+    {name: 'apdu', type: types_.ARRAY, values: types_.OCTET},
     {name: 'successCallback', type: types_.FUNCTION, optional: true, nullable: true},
     {name: 'errorCallback', type: types_.FUNCTION, optional: true, nullable: true}
   ]);