James Isaac

Please see the note in the readme about where tasks must be defined: > Should be called at the top level of your JS, **not** inside a component. This is...

Yup. See the examples at the bottom of the readme. No matter how complex your task is, it should be defined like that.

Yup this would be a good addition, thanks. Although of course want to support both Flow and TypeScript, so shouldn't be deleting the existing `types.js` file. Also, does the current...

But even with your branch, don't the Flow types in `index.ios.js` confuse TypeScript?

@nickmccurdy Yes, agreed. It was my mistake of not thinking outside the default stack RN promotes, which generally does have Flow support. I'll get that and a few other changes...

Isn't TS pretty much always used as a transpiler as well as a typechecker though? Or has this changed with Babel 7?

So you'd expect this to report no type errors, but give a syntax error when it comes to compiling? @elongl Could you confirm whether your project actually compiles and runs...

Thanks, will give it a look over when I get a chance.

No worries, thanks for reporting and the follow up! I'll actually reopen this to remind myself to correct the log message.

My guess is this would be to do with `navigator.geolocation.getCurrentPosition` being code which can't be run in the background. If you take out that line, and make the same fetch...