undefined is not an object (evaluating 'RNBackgroundTimer.setTimeout'

[ocetnik]

undefined is not an object (evaluating 'RNBackgroundTimer.setTimeout'

[the-simian]

I wanted to share that the link command alone did not help me, in the long run I had to link manually. In your src/main/java/com/appname/MainApplication.java

import com.ocetnik.timer.BackgroundTimerPackage;

    @Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
          new MainReactPackage(),
          new VectorIconsPackage(),
          //........and so on
          new BackgroundTimerPackage()
      );
    }

good luck! android build errors in this ecosystem are frustrating sometimes :)

[JimSchofield]

I used react-native link and I checked src/main/java/com/appname/MainApplication.java for the correct links. Still getting the same error here... What might be going on?

[akshayseth]

Not working on expo!

[prayash]

Did you remember to run react-native link after installing the module? I ran into the same issue and running that command fixed it for me.

[pencilcheck]

Works for me after adding the lines in MainApplication.java in addition to the react-native link

[natterstefan]

@the-simian thanks for your comment it did work for me as well now. Wondering why this is not properly working or in the Readme.

[borohhov]

One more thing to the discussion: if you are using remote debugging via Wifi with a real phone, you still need to connect via cable. Remote reloading delivers only the Javascript files, while you need the new app build, which can only be delivered through a cable.

[the-simian]

another thing to check is in your settings.gradle located in the android root has the following entries as well:

include ':react-native-background-timer'
project(':react-native-background-timer').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-background-timer/android')

I know I mentioned it before, but the link command simply did no good for me, and I had to add this stuff myself. Finally I'd (just to cover our bases) make sure you're using latest packages as well. Hope that helps.

@JimSchofield are you getting the exact same stacktrace as this issue? Does it point to the setTimeout, or clear timeout? Just making sure I'm not overlooking something

Best of luck :)

[JimSchofield]

@the-simian gradle entries were identical to what you supplied, and it was identical to the op. For some reason I re-imported it and tried using it and it worked... I wish I could tell you what I was doing wrong. Thanks for the help!

[the-simian]

glad to hear its working for you :)

[ocetnik]

@dadsteph Did previous comments help you? Can I close this issue?

[KenilDomadia]

I am working with expo integrated app, the above steps couldn't solve the issue for me. Is there anything else I can do to solve the issue?

[the-simian]

Right on @natterstefan ~! React Native... sometimes you gotta jiggle the cables you know?

[zorobabel]

@dadsteph Check this comment

@ocetnik I think you can close this issue

[ocetnik]

@akshayseth If you use Expo you'll just need to "eject". Check the installation section in the readme.

[the-simian]

@akshayseth I'm using expo these days also, honestly, I often have problems when I stray from expo's ecosystem unless I eject (which I usually don't because there's a lot of downsides to that)

[haratmalli]

if you were just install this and testing with
BackgroundTimer.runBackgroundTimer(() => { //code that will be called every 3 seconds }, 3000);
and got null is not an object (evaluating 'RNBackgroundTimer.start') error.
You should rebuild app like react-native run-android

[prajna-h]

Not working for me even after linking the module manually. Please help : (

[terrynguyen255]

I'm also facing this problem although I already followed the README (manual linking included) :(