How to update config after refresh token.

[panda919]

Your Environment

• Plugin version:
• Platform: iOS or Android
• OS version:
• Device manufacturer / model:
• React Native version (react-native -v): 0.55.4
• Plugin config

Expected Behavior

Actual Behavior

Context

I used JWT troken auth.
When token is expired, i get new auth token and update BackgroundGeolocation 's config and call sync() function.
BackgroundGeolocation.setConfig({
headers: ------,//new auth token header
reset: true,
});
this.sync();
But, I got 401 error yet.
What's wrong?

Debug logs

[mikehardy]

I'm also interested in this - @panda919 am I correct in saying that in the general sense the question is: If you already launched your app and have this plugin running, what is the best way to dynamically alter it's config?

My case is that I want extra user information available in the "extras" but I only have it available in certain situations and definitely only after app launch. If I'm able to get that info I'd like to alter the info included in extras and have that change take affect

I suppose I/we could do a stop/config/ready-with-reset ? (carefully checking state even)

[panda919]

Actually, I didn't find solution for update config dynamically !!!
While running, even if i update config via setConfig(), token in header is not updated!!!

[mikehardy]

did you try stop/config-with-reset/ready ? basically re-cycling the plugin ? I haven't tried it yet but this was going to be my test

[panda919]

I didn't not stop.
Only reset and call sync().

[panda919]

BackgroundGeolocation.setConfig({
headers: headers,
reset: true,
});
this.sync();

[christocracy]

Yes, #setConfig. No need to #stop. Listen to #onHttp for 401 as your cue to change your token.

Be sure to do that in your HeadlessTask, as well.

[panda919]

BackgroundGeolocation.onHttp(httpEvent => {
        //console.warn('[http] ', httpEvent.success, httpEvent.status);

        let statusCode = parseInt (parseInt(httpEvent.status) / 100 );
        if(statusCode == 4){

           ======================
                    // get new auth token
           =====================
                let headers = {
                  Accept: "application/json",
                  "Content-Type": "application/json",
                  Authorization: "Bearer " +--new token---
                };
                BackgroundGeolocation.setConfig({
                  headers: headers,
                  reset: true,
                });
                BackgroundGeolocation.sync();
      });

this is my source.
But , token is not updated, and i got 401 error yet.
What is wrong?!

[christocracy]

(triple-backtick, with optional language)

let foo = "bar"

[panda919]

thanks. but pls check above my code snipet. what is wrong?
I didn't get expected result for refresh token.

[christocracy]

BackgroundGeolocation.setConfig({
  headers: headers,
  //reset: true,  // <-- reset doesn't apply to setConfig.  remove.
}).then((state) => {
  console.log('- Updated headers: ', state.headers);
  BackgroundGeolocation.sync(); 
});

The plugin's methods are asynchronous. You can't execute #sync until #setConfig completes.

[panda919]

ah, got it.
I will try

[christocracy]

This should also work:

BackgroundGeolocation.onHttp(httpEvent => async {
  await BackgroundGeolocation.setConfig({headers: headers});
  BackgroundGeolocation.sync();
});

[mikehardy]

awesome this will help me too, and I likely would have also forgotten async - thanks @christocracy

[panda919]

thanks very much

[christocracy]

@mikehardy you can't change #extras of a location already persisted to plugin's SQLite db. Updated #extras will be applied to the next recorded location.

[mikehardy]

Yes - until you code up react-native-time-travel I'll have (from my perspective) incomplete data in the past but that's fine - with uids you only need one visible strobe to link things up and that's my use case, so works for me just fine

[1602]

@christocracy when http sync happens in the background (without app running, swiped up to shut down), will onHttp hook still be triggered? I'm asking because I observe app sending outdated tokens over and over again.

As recommended in example from README I'm calling removeListeners() when component unmounts, perhaps it removes onHttp causing http to fail silently without token renewal logic to trigger.

What is recommended approach here?

[christocracy]

swiped up to shut down), will onHttp hook still be triggered?

On Android, of course not. That's what Android Headless Mode is for.

[panda919]

@christocracy
I have 3 question.

• if i have to update config, I have to set {reset: true,} in first config object(meaning init config, not update config value.)
  -if i set schedule config, it is not necessary to call start() function, I may call only startSchedule() function?
  -if i call sync() function, schedule action will continue ?

[christocracy]

if i have to update config, I have to set {reset: true,} in first config object(meaning init config, not update config value.)

In 3.0.4, reset now defaults totrue. You can forget about this now. #ready now always applies the supplied config.

#setConfig is unaware of reset. #reset is not a strict config option of the plugin API itself. It's implemented in the React Native Android code.

-if i set schedule config, it is not necessary to call start() function, I may call only startSchedule() function?

Correct. The Scheduler is a bot that automatically calls #start / #stop for you. Like a cron-task.

-if i call sync() function, schedule action will continue ?

Yes, of course. The HTTP Service is an independent entity that operates upon the SQLite database, selecting records, executing HTTP requests and deleting records when your server says 200.

[panda919]

meaning, stopSchedule function call stop() function automatically implicty?
and startSchedule() call start() function automatically?
Because i got below guide.
http://prntscr.com/nmtq85

[christocracy]

stopSchedule function call stop() function automatically implicty?

Why don't you experiment? No, it only stops the schedule bot.

and startSchedule() call start() function automatically?

#startSchedule starts the bot.

[panda919]

I am meaning.

BackgroundGeolocation.start(() => {    
      BackgroundGeolocation.startSchedule();      
 });   
 BackgroundGeolocation.stopSchedule(() => {      
      BackgroundGeolocation.stop();     
 }); 

this code is correct?

[christocracy]

If you have a schedule configured, why would you explicitly call #start? The schedule-bot will do that automatically according to your configured schedule.

As for the stopSchedule case, that's completely up to you. If the user were logging out, I'd certainly tell the plugin to #stop in that case.