When pjsip app was killed by iOS in background is there a way to get notified and do some final work ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yeah, that is why it bothers me!

On 3/14/13 5:23 PM, samuelv at laposte.net wrote:
> Hi,
>
> You can try Bria 1.3.6 from Counterpath. When you kill the application 
> from the task bar, the application is unregistered of the server. 
> Thus, the application catches the kill event to send a SIP unregister 
> message.
> I know it's not the behavior described by Apple, but thet do it ;-)
>
> Samuel
>
> Le 14 mars 2013 ? 09:02, Pai Peng <sipaipv6 at gmail.com 
> <mailto:sipaipv6 at gmail.com>> a ?crit :
>
>> Hello,
>>
>> again, with or without capturing the uncaught exception in your app, 
>> it will be started by the system automatically. It is a iOS feature 
>> for multitasking app (VoIP).
>>
>> If you want to know why your app is killed, use the uncaught 
>> exception to get the reason.
>>
>>
>>
>> On Thu, Mar 14, 2013 at 8:53 AM, qiulang <qiulang at sinicnet.com.cn 
>> <mailto:qiulang at sinicnet.com.cn>> wrote:
>>
>>     Well, I have to say your reply really does not make sense to me.
>>
>>     In your last reply, you said "the app will be automatically
>>     restarted after killed by system". This time you said "you can
>>     add capturing uncaught exception in your app", you app was killed
>>     without any notice then how can you capture the uncaught exception ?
>>
>>     I am not being rude. Just your reply does not make sense at all.
>>
>>
>>
>>
>>     On 3/14/13 2:26 PM, Pai Peng wrote:
>>
>>         The app does n't get any event , when it is killed by system.
>>         But you can add capturing uncaught exception in your app. In
>>         this way, the client can know why be killed and do something
>>         (write some logs) and by next start read them.
>>
>>
>>
>>
>>         Sent from my iPhone
>>
>>         On 14.03.2013, at 01:00, qiulang <qiulang at sinicnet.com.cn
>>         <mailto:qiulang at sinicnet.com.cn>> wrote:
>>
>>             But how do you define "exited gracefully" ? You are
>>             either killed by iOS or yourself and if you can not tell
>>             difference between them, then how can your something
>>             differently on relaunch ?
>>
>>             Thanks.
>>
>>             Qiulang
>>
>>
>>             On 3/14/13 3:53 AM, John Mah wrote:
>>
>>                 On 2013-03-13 12:34 PM, samuelv at laposte.net
>>                 <mailto:samuelv at laposte.net> wrote:
>>
>>                     You are right some VoIP manage the 'kill -9' like
>>                     skype and other
>>                     application. I asked on apple developer forum abd
>>                     on apple develepor
>>                     support how to do that. Unfortunately, they told
>>                     me they don't
>>                     comment the solution used by other applications.
>>
>>                     Maybe they catch some message of launchd.
>>
>>                     If you resolve the issue, I m interested by your
>>                     solution.
>>
>>                 It is very likely that Skype is detecting the
>>                 ungraceful exit (from the termination) upon
>>                 subsequent relaunch as opposed to catching the
>>                 termination event itself. (One could easily write
>>                 something to NSUserDefaults which says that it exited
>>                 gracefully, and then clear it upon relaunch; if the
>>                 flag isn't present when the app is launched it does
>>                 something different upon relaunch)
>>
>>                 cheers,
>>                 - j
>>
>>                 _______________________________________________
>>                 Visit our blog: http://blog.pjsip.org
>>
>>                 pjsip mailing list
>>                 pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
>>                 http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>>             _______________________________________________
>>             Visit our blog: http://blog.pjsip.org
>>
>>             pjsip mailing list
>>             pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
>>             http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>         _______________________________________________
>>         Visit our blog: http://blog.pjsip.org
>>
>>         pjsip mailing list
>>         pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
>>         http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>>
>>     _______________________________________________
>>     Visit our blog: http://blog.pjsip.org
>>
>>     pjsip mailing list
>>     pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
>>     http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
I
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20130314/6865fa4e/attachment-0001.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux