Skip to content
This repository has been archived by the owner on Mar 15, 2023. It is now read-only.

Commit

Permalink
last of notes
Browse files Browse the repository at this point in the history
  • Loading branch information
aritchie committed Sep 30, 2018
1 parent 5018e47 commit 8ef847a
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 1 deletion.
5 changes: 5 additions & 0 deletions faq.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
## FAQ

Q. When should I schedule my defined jobs? Should I do everytime I start the app.

> When your app starts (Xamarin Forms App.OnStart is a good place). It is a good practice to schedule every start. The framework will only update jobs if one already exists.
Q. How long does the background sync let me have on iOS

> 30 seconds and not a penny more
Expand All @@ -24,6 +28,7 @@ Q. Is there job priorization?

> Not yet - debating this one for the future

Q. Why can't I set the next runtime

> From a true runtime perspective you can't, however, inside you job you can set add/update the job parameters or check the last runtime on the job info to see if you want to run. Example below:
Expand Down
3 changes: 2 additions & 1 deletion platform_android.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,5 @@ Plugin.Jobs.CrossJobs.Init(this, savedInstanceState); // activity


### NOTES
* If Doze is enabled, the reschedule period is not guaranteed to be an average of 10 mins. It may be much longer.
* If Doze is enabled, the reschedule period is not guaranteed to be an average of 10 mins. It may be much longer.
* IF YOU ARE NOT SCHEDULING YOUR JOBS ON EVERY START - If you application force quits, Android will not restart the job scheduler. For this, there is CrossJobs.EnsureJobServiceStarted

0 comments on commit 8ef847a

Please sign in to comment.