Reorder register app response to mobile and hmi

If an HMI activates an application immediately after receving a
register app notification, then the mobile application could receive a
HMI FULL notification from the activation and then an HMI NONE
notification. The HMI NONE notification comes from the resumption
function following the HMI and mobile responses.

By sending the HMI notification last, we can ensure that resumption will
follow before the HMI sends an `ActivateApp`. With this commit, the
mobile application will first be notified of successful registration and
then the HMI will be notified.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/components/application_manager/src/commands/mobile/register_app_interface_request.cc b/src/components/application_manager/src/commands/mobile/register_app_interface_request.cc
index e9f6db05b2..54c58dbb1a 100644
--- a/src/components/application_manager/src/commands/mobile/register_app_interface_request.cc
+++ b/src/components/application_manager/src/commands/mobile/register_app_interface_request.cc
@@ -590,9 +590,9 @@ void RegisterAppInterfaceRequest::SendRegisterAppInterfaceResponseToMobile() {
                                             application->mac_address());
   }
 
+  SendResponse(true, result_code, add_info.c_str(), &response_params);
   SendOnAppRegisteredNotificationToHMI(
       *(application.get()), resumption, need_restore_vr);
-  SendResponse(true, result_code, add_info.c_str(), &response_params);
 
   // Check if application exists, because application might be unregestered
   // during sending reponse to mobile.