I am working on (React native app) use tracking location app . Getting location updates every second eigther my app forground or background . (Not work in background ).
Probelm is when app is backgroud after 5 minutes my app killed .
App working on 9 version . Note: Background location service not work on version 11 and 12 on android
Let me know if any one do this .
Thanks.
Related
I am creating a react native app for location tracking so I wanted to know how can I work with it.
Requirements:
Start tracking location on button click.
Fetch both foreground and background location.
Fetch location even when the app is killed.
Application needs to work with latest Android Version.
Please let me know how can I complete all the above requirements with stable packages.
In my app I want to implement backgroud file sync to the database using react-native-background-task. It is working for IOS but not working for android. Can anyone give some solution which will work for both IOS and android
No, it just doesn't work well. I have been trying since 4 month and searching info I reach to the fact that just is a feature that is not well implemented in React-Native.
I'm developing a react-native app and I'm facing a problem: I need to execute a periodical task (an API call to post some data) in all possible cases: the app is in the background, app is in foreground and app is killed (double tap on the home button and swipe up).
How could I achieve this in iOS?
For Android, HeadlessJS seems to work fine, but for iOS I couldn't find anything which could fit my case.
I've tried with react-native-background-fetch but if the app is killed, also the background fetch is halted (https://github.com/transistorsoft/react-native-background-fetch/issues/34)
I've tried react-native-background-timer, but it works only until the app is killed.
I've also tried adding a geolocation native library to set background mode "location updates" capability, and calling its start method inside the didFinishLaunchingWithOptions into AppDelegate.m. But also this works only until the app is killed.
If I use the same native library on a native iOS app, and I call it inside the same method into AppDelegate.m, it keeps working also when the app is killed.
So which is the difference between the native and react-native app that lets the app survive the force-quit?
I've also tried reading this https://developer.apple.com/library/archive/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/BackgroundExecution/BackgroundExecution.html but I couldn't replicate that info via react-native.
Can someone help me, please?
I have an expo app that is causing issues on some phones when launching. Haven't had this issue with the same phone before but haven't opened it on said phone for over a month.
Initially I had 3 test devices and 2 of them were in use everyday, third was only used once to open and test small functionality and then recently (causing this issue).
After Launching app
How its supposed to look
Expo SDK: 30
Devices:
iPhone 5c -- Works |
Samsung S6 -- Works |
Google Pixel -- Doesn't Work |
Samsung S7 Edge -- Doesn't Work
Things Tried:
Build and Download APK (unknown sources) -- Same Result |
Publish to Expo and Open with app (under profile) -- Same Result |
Connect via CLI (Tunnel & same Network) -- Same Result
** all of these with the exception of APK worked on these devices prior (few weeks)
I found the issue
Basically, I had a SwitchNavigator and for w.e reason the app was loading that particular page. For those who have this issue, if you have a device that has this app and you make changes, check the routing to the switch navigator and ensure it doesn't render this first.
For me it was part of the auth flow so it was rendering first but there was some logic that made this particular screen inaccessible for the devices.
Solution 1: make the switch nav a stack or tab
Solution 2: check validation and add logic to pass switch if not needed
Solution 3: remove routing to this page
I have created a Sencha Touch 2.3 app and tried to build it on iPhone5 using xcode. Sometimes when I deploy it, the phone freezes and then the only choice left is to force a reboot.
This happens occasionally only while trying to build it.
Has anyone else come across this ?
At first, I assumed it happens once in a while only while trying to build and deploy it.
But recently, someone reported a similar issue with another sencha app on an iPhone5 which was already downloaded and used several times. While launching this app, the screen went white and after a while the phone rebooted !
Is Sencha Touch apps causing this ?