What's the best practice to communicate from the foreground app to the background app?

With Background.exit({...}) it is very easy and convenient to communicate background -> foreground. But is there a way to do the other way: foreground -> background. Kind of sending a job or a message?

Top Replies

jim_m_58 over 2 years ago +3 verified

The only way to pass info into the background service is to use Application.Properties or Application.Storage. In general, I only use Properties if there is are settings associated with it.

All Replies

0 jim_m_58 over 2 years ago in reply to flocsy🤠

With ciq 1.x apps, you can't use a background service. With some API levels, you don't have Appication.Storage, These are things you need to design for. I've done it, so I know it's possible.

With a DF, you may just need to restrict your app to those devices with backgrounding,

0 DaveBrillhart 11 months ago

Did you figure this out? Jim suggest it is possible but didn't share the approach. I need to be able to inform the BG process with something as simple as a true/false flag. To an EDGE 1000 type device that can't access Storage from the BG. So the 2nd time it runs it returns the rest of the data I need using exit(). Thanks flocsy🤠

0 flocsy🤠 11 months ago in reply to DaveBrillhart

No, I gave up

0 _psx_ 11 months ago in reply to DaveBrillhart

Where is the problem?