How to run multiple instances of background-fetch?

Your Environment

• Plugin version:2.7.0
• Platform: iOS and Android
• OS version:
• Device manufacturer / model:
• React Native version (react-native -v):0.60.3
• Plugin config

Expected Behavior

Initiating background-fetch in deferent parts of app with deferent callbacks, without overwriting any background-fetch previous process

Actual Behavior

Last background-fetch Initiation overrides the previous one

Steps to Reproduce

1.put code to intiate background-fetch in a separate class
2. instantiate background-fetch class in other components with a callback provided as an argument

background- fetch class:

import BackgroundFetch from "react-native-background-fetch";


export default class BackgroundFetch {

  constructor(fetchFunction){
    this.fetchFunction = fetchFunction;
  }


  initBackgroundFetch() {
    // Configure it.
    BackgroundFetch.configure({
      minimumFetchInterval: 15,     // <-- minutes (15 is minimum allowed)
      // Android options
      stopOnTerminate: false,
      startOnBoot: true,
      requiredNetworkType: BackgroundFetch.NETWORK_TYPE_NONE, // Default
      requiresCharging: false,      // Default
      requiresDeviceIdle: false,    // Default
      requiresBatteryNotLow: false, // Default
      requiresStorageNotLow: false  // Default
    }, () => {
      console.log("[js] Received background-fetch event");
      this.fetchFunction();
      // Required: Signal completion of your task to native code
      // If you fail to do this, the OS can terminate your app
      // or assign battery-blame for consuming too much background-time
      BackgroundFetch.finish(BackgroundFetch.FETCH_RESULT_NEW_DATA);
    }, (error) => {
      console.log("[js] RNBackgroundFetch failed to start");
    });

    // Optional: Query the authorization status.
    BackgroundFetch.status((status) => {
      switch(status) {
        case BackgroundFetch.STATUS_RESTRICTED:
          console.log("BackgroundFetch restricted");
          break;
        case BackgroundFetch.STATUS_DENIED:
          console.log("BackgroundFetch denied");
          break;
        case BackgroundFetch.STATUS_AVAILABLE:
          console.log("BackgroundFetch is enabled");
          break;
      }
    });
  }
}

instantiating in other components:

async componentDidMount() {
    await this.checkInternet();
    const backGroundFetchHome = new BackgroundFetchClass(this.checkInternet.bind(this))
    backGroundFetchHome.initBackgroundFetch();

  }
async componentDidMount() {
    this.main();
    const backGroundFetchChat = new BackgroundFetchClass(this.main.bind(this))
    backGroundFetchChat.initBackgroundFetch();
 
  }

[christocracy]

Can you please elaborate more on this.

Think of a background-task as a balloon. Each background-fetch callback is a pin poking the balloon when #finish is called. The first pin that pops the balloon terminates the task. If each task were executing an HTTP request, one request may not complete.

[medmo7]

thanks i will close this issue