task-manager | Task Manager Is An Easy To Use Task Manager | Job Scheduling library

Well after a week of battling it I finally found a solution. It turns out that the reason I am getting this error is simply because I am running this code on Expo which does not allow background location fetching. There is nothing wrong with the code, all I had to do was to build a standalone App (expo build:android) and the standalone version of the App worked just fine and could fetch background location 😁

I also passed an extra parameter to my Location.startLocationUpdatesAsync which increased the effectiveness of background-location fetching and actually allowed me to visualize that the App is fetching the background-location via a notification like this:

There are two major reasons for this cause.

1. Setting enableDangerousExperimentalLeanBuils to true.
2. Missing expo-splash-screen package.

The error is because it's(Gradle build) looking for expo-modules-splashscreen package, which is supposedly moved out of expo's main module in SDK 41, hence needs to be separately installed. In order to fix this, there are two workarounds:

1. Remove enableDangerousExperimentalLeanBuilds property. (Not tested)
2. Install expo-splash-screen using npm install expo-splash-screen.(Tested and working)

Replace your code with this code:

I don't believe there's anything more you can do. The Flink scheduler will try to co-locate consumer tasks with their producers, in order to leverage optimizations in the network stack. (Shared memory is used instead of netty whenever two communicating tasks are in the same JVM.) As I understand it, cluster.evenly-spread-out-slots: true is really only relevant for sources, which don't have input preferences.

It's often the case that reducing the parallelism for part of the job is counter-productive, as it forces a network shuffle (perhaps preventing operator chaining), and creates skew in the load on the task slots.

Solved on Expo Forum (https://forums.expo.io/t/push-notification-unable-to-retrieve-the-fcm-server-key-for-the-recipients-app-make-sure-you-have-provided-a-server-key-as-directed/48529/2)

@adamjnav creating a new project I could see that I forgot of set my experienceId: "@myexpouser/myproject" and my app.json android: { …, “useNextNotificationsApi”: true, “adaptiveIcon”:"… }

I have also updated Expo for SDK40, same problem, so that's why i just again installed 38 that is much more better and optimized, try to write to their expo - community: Expo-Community, and expo - devs and admins are there

hope i could help you! https://forums.expo.io/

To anyone who is looking at this later, please make sure that you test your app on a physical device. Emulator doesn't really support the task manager and background fetch properly!

MongoDB has two connection string formats. The old format is now deprecated and uses an old URL format. There are mongodb+srv:// URLs, and simple mongodb:// URLs. If you are using the new format (you probably are by default), the new URL parser drops support for the old style urls.

useCreateIndex: Again previously MongoDB used an ensureIndex function call to ensure that Indexes exist and, if they didn't, to create one. This too was deprecated in favour of createIndex. the useCreateIndex option ensures that you are using the new function calls.

Reference:

https://mongoosejs.com/docs/connections.html#options https://mongoosejs.com/docs/deprecations.html

Based on your service and ngOnInit code. Seems like the type that you have specified on your this.taskService.getTasks and this.taskService.getLists doesn't correlate with the return type of your service

Your Code