Languages

Menu
Sites
Language
Receiving Hangup Signal from Tizen Push Deamon & Application is terminated

We have implemnted Tizen Push service to receive notifications. Whenever we received notification, we are receivng a hangup signal from Tizen Push Daemon . Due to this our application is being terminated by tizen system.

Below are the logs.

07-27 18:34:55.323 : DEBUG / Messenger ( 14407 : 14407 ) : recieved Name = Kumar Das 
07-27 18:34:55.533 : WARN / AUL_AMD ( 444 : 444 ) : amd_key.c: _key_ungrab(250) > fail(-1) to ungrab key(XF86Stop)
07-27 18:34:55.533 : WARN / AUL_AMD ( 444 : 444 ) : amd_launch.c: __e17_status_handler(2132) > back key ungrab error
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortIpcServer.cpp: OnReadMessage(728) > _MessagePortIpcServer::OnReadMessage
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortIpcServer.cpp: HandleReceivedMessage(567) > _MessagePortIpcServer::HandleReceivedMessage
07-27 18:34:55.543 : ERROR / MESSAGE_PORT ( 386 : 408 ) : MessagePortIpcServer.cpp: HandleReceivedMessage(577) > Connection closed
07-27 18:34:55.543 : ERROR / MESSAGE_PORT ( 386 : 408 ) : MessagePortIpcServer.cpp: HandleReceivedMessage(599) > All connections of client(14407) are closed. delete client info
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortStub.cpp: OnIpcClientDisconnected(172) > MessagePort Ipc disconnected
07-27 18:34:55.543 : ERROR / MESSAGE_PORT ( 386 : 408 ) : MessagePortStub.cpp: OnIpcClientDisconnected(175) > Unregister - client =  14407
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortService.cpp: UnregisterMessagePort(207) > _MessagePortService::UnregisterMessagePort
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortService.cpp: unregistermessageport(190) > unregistermessageport
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortService.cpp: unregistermessageport(190) > unregistermessageport
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortService.cpp: unregistermessageport(190) > unregistermessageport
07-27 18:34:55.543 : INFO / MESSAGE_PORT ( 386 : 408 ) : MessagePortService.cpp: unregistermessageport(190) > unregistermessageport
07-27 18:34:55.553 : ERROR / PUSHD ( 866 : 866 ) : spp.c: _receiving_from_app_cb(1773) > async connection callback ch 0xb43131b8: HUP
07-27 18:34:55.553 : INFO / AUL_PAD ( 455 : 455 ) : sigchild.h: __launchpad_sig_child(142) > dead_pid = 14407 pgid = 14407
07-27 18:34:55.553 : INFO / AUL_PAD ( 455 : 455 ) : sigchild.h: __sigchild_action(123) > dead_pid(14407)
07-27 18:34:55.553 : INFO / AUL_PAD ( 455 : 455 ) : sigchild.h: __sigchild_action(129) > __send_app_dead_signal(0)
07-27 18:34:55.553 : INFO / AUL_PAD ( 455 : 455 ) : sigchild.h: __launchpad_sig_child(150) > after __sigchild_action
07-27 18:34:55.573 : INFO / Tizen::System ( 1032 : 1032 ) : (246) > Terminated app [org.Messenger.tizen.msgapp]
07-27 18:34:55.573 : INFO / Tizen::Io ( 1032 : 1032 ) : (729) > Entry not found
07-27 18:34:55.573 : INFO / Tizen::App ( 992 : 992 ) : (243) > App[org.Messenger.tizen.msgapp] pid[14407] terminate event is forwarded
07-27 18:34:55.573 : INFO / Tizen::System ( 992 : 992 ) : (256) > osp.accessorymanager.service provider is found.
07-27 18:34:55.573 : INFO / Tizen::System ( 992 : 992 ) : (196) > Accessory Owner is removed [org.Messenger.tizen.msgapp, 14407, ]
07-27 18:34:55.573 : INFO / Tizen::System ( 992 : 992 ) : (256) > osp.system.service provider is found.
07-27 18:34:55.573 : INFO / Tizen::App ( 992 : 992 ) : (506) > TerminatedApp(org.Messenger.tizen.msgapp)

 

Help in this regard is appriciated.

Thanks,

Bharath

List

Responses

3 Replies
colin Rao

Hi, I don't have the push service experience on Tizen. But as your error log: "07-27 18:34:55.533 : WARN / AUL_AMD ( 444 : 444 ) : amd_key.c: _key_ungrab(250) > fail(-1) to ungrab key(XF86Stop)", seems the Tizen can't get the pushed message key/vaule correctly, possible it's the message string(key/value) validate issue.

I've searched from the development tutorials on this site, below link is Samsung guide for push service on Tizen, post here as your reference. :)

https://developer.tizen.org/development/tutorials/native-application/messaging/push

Jeongsu Kim

07-27 18:34:55.553 : ERROR / PUSHD ( 866 : 866 ) : spp.c: _receiving_from_app_cb(1773) > async connection callback ch 0xb43131b8: HUP

means that push service daemon received that your app has been terminated.

your app terminated -> push service noticed (O)
push service terminates your app (X)

 

No more helpful information is not in the logs.

Vikram

from the log we cant get enough info to analyze the root cause. 

it's better if you can share the related sample code here. :)