Benjamin Portman

Just tried this fix and it still doesn't work on android for me. Is it needed on all parent containers, or just the immediate parent?

Hey - so I fixed this ages ago and can't be 100% sure, but looking at my commits I think my problem was trying to absolutely position the action button...

The recent commit changing `setTimeout` to `this.setTimeout` in the backgroundClockMethod() function seems to have helped matters but not completely solved the problem. I have this issue but the background event...

I was able to use this workaround to get my background timer running in the background non-stop even with the phone locked and screen off: https://github.com/ocetnik/react-native-background-timer/issues/9#issuecomment-291562476

That was a bad solution - the timer stops after 3 minutes if the user plays audio in another app. Still hunting for something that works without the "silent audio...

From my investigations it's more possible on Android, but iOS there is not a way to guarantee a background process persists permanently. Even with playing a silent audio in the...

The only thing they gave me a hard time about was background audio. They said nothing the first two versions I submitted, but for the 3rd version they kept rejecting...

Actually, it doesn't work for me in release or debug, unless I play a silent audio in the background. If I don't play an audio in the background the process...

Since my last post I've learned that the silent audio is only needed when the device is unplugged from power. When it's plugged in I can get a consistent, unending...

I solved this issue in debug with this: https://github.com/ocetnik/react-native-background-timer/issues/9#issuecomment-291562476 Crossing my fingers it works in release configuration as well.