🐛 Bug Report

Environment

Expo CLI 2.20.8 environment info:
System:
OS: macOS 10.14.5
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.14.2 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
expo: ^33.0.0 => 33.0.3
react: 16.8.3 => 16.8.3
react-native: https://github.com/expo/react-native/archive/sdk-33.0.0.tar.gz => 0.59.8
react-navigation: ^3.11.0 => 3.11.0
npmGlobalPackages:
expo-cli: 2.20.8

Steps to Reproduce

When the app in foreground and background - location tracked and stored in database, when the app killed - background task killed - no request is going in database.

Expected Behavior

Location should be stored also when the app is killed

Actual Behavior

I don't think I missed some additional options - because all works in background. I also know that for iOS it's needed to walk more than 500m. Also one question - what could be defined in background task when it's killed? Could we use AsyncStorage, or simple fetch to send data to database or using moment or axios? Are there any limits? Because previously when I didn't eject - all this logic was working fine... Any ideas and helps will be really appreciated