Losing handle to jobs after app termination & restart about react-native-background-job

[vikeri]

Do you mean that it is executing in the foreground? There are some issues with alwaysRunning and we will probably replace it with an exact mode in v.2.0.0. If you wish to try it out already please try adding [email protected]

[brwelch]

It seems to think that the app is still in a terminated state when in fact I've restarted my app (so the job keeps running, I can't cancel it). I'll give 2.0.0 a try. Is there a different API / set of parameters or methods for exact mode?

[vikeri]

Ok, weird. And before you try 2.0.0, what current version are you using?

[brwelch]

I'm using 1.2.4. I just tried 2.0.0 (switched alwaysRunning --> exact), this issue is not exhibited which is great. I'm seeing something funky with the intervals, it seems like from logcat that RNBJ is executing at the exact intervals, but my API calls seem to be at scattered times (which was fine in 1.2.4) - this could be on my end and will investigate. Though are there any known issues with V2 exact mode in terms of the intervals?

Also, it looks like it's now possible to have multiple exact jobs (as opposed to only one alwaysRunning) and they can also run in the foreground? (appreciating that these should be concise units of work so as to not freeze the app)

[vikeri]

I have just started evaluating v2 and I'm not personally using exact mode. But I tried it and it worked. A way to debug is to fork this project and try the example project and see if you have the same issues there.
Yes they can run in the foreground, I haven't tested multiple exact jobs since I did not develop that feature.

[brwelch]

Thanks a lot. What branch/repo is the v2 code on?

[vikeri]

It's in this PR: #38 Can I close the issue btw?

[brwelch]

Thanks; yes given that 2.0 solves it. Appreciate all the quick responses.

[vikeri]

👍