BackgroundTimer.runBackgroundTimer() does not run in background
See original GitHub issueOn Android, BackgroundTimer.runBackgroundTimer()
pauses the task when the Activity is moved to background. This doesn’t seem intuitive given that it’s meant to be a background timer.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:9 (1 by maintainers)
Top Results From Across the Web
node.js - React-Native IOS: Background-Timer doesnt run in ...
runBackgroundTimer (() => { //code that will be called every 3 seconds } ... code will be performing for iOS on background too...
Read more >How to use the react-native-background-timer ... - Snyk
runBackgroundTimer function in react-native-background-timer ... Use Snyk Code to scan source code in minutes - no build needed - and fix issues immediately ......
Read more >How to run timer in background for… | Apple Developer Forums
We have an app that connects to a bluetooth device(Beacon) and sends and receives BLE data in the background. There is no problem...
Read more >How to Make a React Native Background Countdown Timer ...
The code in this tutorial should work on both Android and IOS. ... install the background timer package, and then run the project...
Read more >react-native-background-timer - npm
Don't call .start() twice, as it stop performing previous background task and starts new. If it will be called on backgound no tasks...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@mun3 @roysG @nervouscat @johntitus you can try
yarn upgrade react-native-background-timer@2.1.0-alpha.5
If you install from github instead of NPM, so you get the latest codebase with @hawkup’s commit, it fixes the issue.