Languages

Menu
Sites
Language
background-network manifest not working after disconnecting and reconnecting

Are there any known workarounds for background-network manifest not working after disconnecting and then connecting to a network? I am working on an application that is intended to continuously ping a server would like for the application to continue to ping the server in the background after reconnecting 

List

Responses

4 Replies
HwanKyu Jhun

If an application only has background-network category in the tizen-manifest.xml, the application will be frozen when network is disconnected.

Background-network category is different from other categories.

If you want to make your application that is running in the background after network is disconnected, you should add another background-category in the tizen-manifest.xml.

https://developer.tizen.org/development/guides/native-application/applications/ui-application/efl-applications/basic-ui-application#allow_bg_table

e.g. download category.

Dawson Patel

Thanks for your reply. 

I have a follow-up question

Will the solution you suggested of adding another background category work  if the only thing I want to do in the background is http get requests?

Dawson Patel

Thanks for your reply. 

I have a follow-up question

Will the solution you suggested of adding another background category work  if the only thing I want to do in the background is http get requests?
 

HwanKyu Jhun

Yes.

Background-network category allows the app to work in the background only when the network is connected.

If the app only has background-network category in the tizen-manifest.xml, the app will be frozen when the network is disconnected.

I think this question is related to https://bugs.tizen.org/browse/TW-86.

As far as I mentioned in TW-86, it works fine.

If you find strange things related to this, please attach reproduced logs to JIRA (TW-86).
Thanks.