AccessToken is getting removed after app refresh

[knappdev]

I have configured my feathers app to store token AsyncStorage. But seems like access token is getting removed when the app is reloaded.

export const restApp = feathers()
  .configure(rest(host).superagent(superagent))
  .configure(hooks())
  .configure(authentication({
    storage: AsyncStorage,
  }))

Package details:

    "feathers": "^2.1.1",
    "feathers-authentication-client": "^0.3.2",
    "feathers-errors": "^2.7.1",
    "feathers-hooks": "^2.0.1",
    "feathers-rest": "^1.7.2",
    "feathers-socketio": "^1.6.0",

    "react": "^16.0.0-alpha.6",
    "react-native": "^0.44.0",

[keesee]

Took a quick peek. this is because Async store return a promise, not a value. it seems the token is still in my storage, but getJWT isn't return the proper value for feathers to set in its settings store. I don't have time to tackle this today but will post something when I do for those struggling with this.

[daffl]

The authentication client should take asynchronous storages into consideration but if it is a RN update we might have to fix something.

[jamesholcomb]

Also seeing this issue with RN 0.46. AsyncStorage is not cleared on app().logout()

[thngdude]

Also happening on RN 0.45.1 with simulator. AsyncStorage seems to be broken. Calling #clear and #removeItem don't work (#clear left one key in the store). app.logout() doesn't clear the accessToken from the store.

[thngdude]

@keesee From what version of RN did you upgrade from, before going to RN0.44?

[olivier-o]

@daffl, any update on this issue?

[ekryski]

We'll double check this. Haven't noticed an issue in some of the apps we've worked on but we haven't been looking for this specifically.

app.logout() returns a promise so if you're checking things after the fact you'll want to do

app.logout().then(() => {
  AsyncStorage.getAllKeys().then(keys => {
    console.log(keys); // should not have the feathers-jwt
  });
});

[olivier-o]

my concern is more on the refresh part. when refreshing the page with an authenticated user the token is somehow lost in the request header and the service call fails despite the fact the token is still present in the local store.
Is there any work around to manually set headers before the request fires?

[ekryski]

@olivier-o Not sure what you mean by "refresh the page" if we're talking about React Native, but if you lose your connection or you refresh the page in the browser then you should re-authenticate before you do any other action.

However, yes you can use hooks. So you can create a before all hook that sets the header for every service request. With the client side REST plugin, this already happens here, so you must be making requests before you have re-authenticated or you are using sockets and maybe somthing is timing out, which is related to #64.

In any case, this is how you set headers explicitly.

const client = feathers();

  client.configure(hooks())
    .configure(rest(`http://localhost:${port}`).axios(axios))
    .configure(auth({ storage: localStorage }));

client.hooks({
      before: {
        all: [
          hook => {
            hook.params.headers = {
              'Authorization': `${apikey}`
            };
          }
        ]
      }
    });

[olivier-o]

@ekryski, thanks work great. I just applied that at my service level not at client level, cause when calling the userService, there is no token yet.

[radiegtya]

still not working on my react app.. any workaround?

[daffl]

When you have a token in storage you have to call app.authenticate() with no parameters as shown in the examples of the feathers chat.