This is a new React Native project, bootstrapped using @react-native-community/cli.
To reproduce the bug, simply run the app following react-native guide.
- Then click on the bug blue "Register background fetch" button. (This will register a background task)
- Then you can kill your app and run the background task with
adb shell cmd jobscheduler run -f com.rnbgfetchbugrepro 999- You should see a logger in the metro console indicating the task started, stopped, and finished.
- Then re-open the app and reclick the button
- Re-kill your app and re-run the headless task with
adb shell cmd jobscheduler run -f com.rnbgfetchbugrepro 999- You should now see an error in the logcat console
[BGTask] failed to load config for taskId: react-native-background-fetch
- You should now see an error in the logcat console
rnbgfetch-repro.mp4
From my research, I noticed that the second time we register the background task, it is not properly saved into the shared-preferences (We can see it in the video). This happens because on this line, the mConfig hashmap still contains the taskId when we relaunch the app the second time.
And the hashmap still contains the taskId because when we call stop(), it clean the shared-preferences, but not the mConfig hashmap.
That is why we see a Re-configured existing task, instead of a fresh "configure".
Then when we try to run the background task, it loads the config from the shared-preference, but it can't find nothing. So it fails with [BGTask] failed to load config for taskId: react-native-background-fetch
We should probablu clear the mConfig object when we stop the backgroundTask, so that there is no "desynchronisation" between the sharedPreference
Note: Make sure you have completed the React Native - Environment Setup instructions till "Creating a new application" step, before proceeding.
First, you will need to start Metro, the JavaScript bundler that ships with React Native.
To start Metro, run the following command from the root of your React Native project:
# using npm
npm start
# OR using Yarn
yarn startLet Metro Bundler run in its own terminal. Open a new terminal from the root of your React Native project. Run the following command to start your Android or iOS app:
# using npm
npm run android
# OR using Yarn
yarn android# using npm
npm run ios
# OR using Yarn
yarn iosIf everything is set up correctly, you should see your new app running in your Android Emulator or iOS Simulator shortly provided you have set up your emulator/simulator correctly.
This is one way to run your app — you can also run it directly from within Android Studio and Xcode respectively.
Now that you have successfully run the app, let's modify it.
-
Open
App.tsxin your text editor of choice and edit some lines. -
For Android: Press the R key twice or select "Reload" from the Developer Menu (Ctrl + M (on Window and Linux) or Cmd ⌘ + M (on macOS)) to see your changes!
For iOS: Hit Cmd ⌘ + R in your iOS Simulator to reload the app and see your changes!
You've successfully run and modified your React Native App. 🥳
- If you want to add this new React Native code to an existing application, check out the Integration guide.
- If you're curious to learn more about React Native, check out the Introduction to React Native.
If you can't get this to work, see the Troubleshooting page.
To learn more about React Native, take a look at the following resources:
- React Native Website - learn more about React Native.
- Getting Started - an overview of React Native and how setup your environment.
- Learn the Basics - a guided tour of the React Native basics.
- Blog - read the latest official React Native Blog posts.
@facebook/react-native- the Open Source; GitHub repository for React Native.