Background fetch, testing problems

Question

I have a react-native application which includes react-native-background-task which uses react-native-background-fetch. I configured a job to console.log a simple message when it runs. I understand that the background fetch is not working on simulator, but you can test it by going into Debug -> Simulate background fetch. When I hit this, the app goes to background. I did not get any output. I have enabled background fetch in Info.plis and also the code returns status.available when I check with the library function. How do you actually test this?

Xcode 8.3.3
react-native 0.44.0
react-native-background-fetch 2.0.8 
react-native-background-task 0.2.1



class App extends Component {
componentWillMount() {
  BackgroundTaks.define(() => {
    console.log('==================FETCH==================');
    console.log('task running');
    console.log('====================================');

    BackgroundTaks.finish();
  });
}

componentDidMount() {
  BackgroundTaks.schedule();
}

render() {
  return (
    <Router />
  );
}}

export default App;

I am getting the same breakpoint when I Simulate background fetch using real device

libsystem_kernel.dylib`mach_msg_trap:
    0x186e9721c <+0>: mov    x16, #-0x1f
    0x186e97220 <+4>: svc    #0x80
->  0x186e97224 <+8>: ret

Xcode menu > Debug > Simulate Background Fetch

Desdenova
– Desdenova

2017-09-22 07:04:18 +00:00
Commented Sep 22, 2017 at 7:04 — Desdenova
– Desdenova, Commented Sep 22, 2017 at 7:04
@Desdenova That is what I am doing, did you read it ?

parohy
– parohy

2017-09-22 07:08:53 +00:00
Commented Sep 22, 2017 at 7:08 — parohy
– parohy, Commented Sep 22, 2017 at 7:08
Appearantly not :) Sorry

Desdenova
– Desdenova

2017-09-22 07:10:53 +00:00
Commented Sep 22, 2017 at 7:10 — Desdenova
– Desdenova, Commented Sep 22, 2017 at 7:10
Please add minimal reproducible example

bennygenel
– bennygenel

2017-09-22 07:11:55 +00:00
Commented Sep 22, 2017 at 7:11 — bennygenel
– bennygenel, Commented Sep 22, 2017 at 7:11

parohy · Accepted Answer · 2017-10-13 08:16:48Z

1

Solved. At the end I realized the background fetch checkbox was not checked in the project settings. After checking it does work.

answered Oct 13, 2017 at 8:16

parohy

2,1992 gold badges25 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

prabodhprakash · Accepted Answer · 2017-09-22 07:13:48Z

0

Since you've mentioned that you've tried writing to storage also - which is not working - my updated answer would be: while you are running background fetch, you can at the same time hit a server on which you can see the logs. That way, you can tell, if the background fetch was successfully working.

I've created a hackable localTestingServer that you can fork and get started immediately.

edited Sep 22, 2017 at 7:13

answered Sep 22, 2017 at 7:08

prabodhprakash

3,94729 silver badges52 bronze badges

3 Comments

parohy Over a year ago

I edit the question. I tried using storage as well but there was no result after simulating background fetch. I even installed it on the device and let it run for a while but the storage was not updated

parohy Over a year ago

How does this lead to narrowing down the possible problem, when all I do is run a background task to set a dummy string to storage or print an output? It does not run the task at all and throws the exception I added to the question.

prabodhprakash Over a year ago

Because now you can send logs to some server in place. Depends on your imagination to solve a problem

Collectives™ on Stack Overflow

Background fetch, testing problems

2 Answers 2

Comments

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related