[M76 Migration][Service][Global] Fix Failure of Onstop 52/226852/2 accepted/tizen/unified/20200311.130927 submit/tizen/20200309.024114 submit/tizen/20200310.042712
authork2.nagaraju <k2.nagaraju@samsung.com>
Tue, 28 Jan 2020 13:21:39 +0000 (18:51 +0530)
committerYoungsoo Choi <kenshin.choi@samsung.com>
Fri, 6 Mar 2020 04:12:33 +0000 (20:12 -0800)
This guarantees success callback of start API can be called
when launching process is completely finished.

Reference: https://review.tizen.org/gerrit/223323/

Change-Id: I56c2bc28501a94f9bffc4f499b94b54c622ca61f
Signed-off-by: k2.nagaraju <k2.nagaraju@samsung.com>
wrt_app/service/main.js

index a37e977..3ae77a6 100755 (executable)
@@ -78,6 +78,7 @@ wrt.on('start-service', (event, internal_id, permissions) => {
     sandbox[internal_id]['stopped'] = undefined;
     const start_callback_string = 'if (module.exports.onStart !== undefined) { module.exports.onStart(); }';
     vm.runInContext(start_callback_string, sandbox[internal_id]);
+    wrt.finishStartingService(internal_id);
   }
   const request_callback_string = 'if (module.exports.onRequest !== undefined) { module.exports.onRequest(); }';
   vm.runInContext(request_callback_string, sandbox[internal_id]);