right.. okay!

well.. lmk if you have any more questions 🙂

Thanks for the assistance!

Also, can you please add me as a friend so I can DM you? Thanks

👍 donezo

Hi, I am new to supertokens & I need assistance using it with a React-Native app. I would appreciate every assistance, Thanks.

hey @User , what's your backend in? Also, for RN, we only support sessions at the moment.

@rp I thanks for ur assistance, I would be spinning up a node server now

@User , one more thing, if you want to use the login APIs provided by us along with sessions, we will first need to update the react native SDK to work with the latest version of the core..

We don't have bandwidth for that now, but you can contribute the update.. will be happy to get on a call.

I would be glad to

Can you talk right now

awesome! I'm a bit busy right now.. but you can pick a slot for sometime tomorrow here: https://calendly.com/supertokens-rishabh/20-mins

Aiit

👍

Hello! Does anyone know how to use

Session.getJWTPayloadSecurely()

to get user payload (eg. username) with UTF-8 encoding? For now it returns me data with werid characters like:

łukasz123

instead of

Łukasz

🙂

Interesting.. I think this may be a bug in how we encode the token.

We do:

let tokenInfo = {
  uid: userId,
  ate: atExpiry,
  up: jwtPayload //  contains your user's name
}
let frontToken = Buffer.from(JSON.stringify(tokenInfo)).toString("base64")

The above is in the backend.. Then on the frontend, we do:

let tokenInfo = JSON.parse(atob(frontToken));
return tokenInfo.up;

If you know where the error might be in the above, please lmk.. otherwise i'll figure it out anyway (soon)

I've also opened an issue for the same: https://github.com/supertokens/supertokens-node/issues/134

Great, thanks for the quick response!

And on the frontend side, the deserialising happens here: https://github.com/supertokens/supertokens-website/blob/master/lib/ts/fetch.ts#L97

So if you need this fixed urgently, you can fork these repos and use them in your project. FYI: supertokens-website (which does sessions) is being used inside supertokens-auth-react

There must be a bug somewhere, because for the code below I got:

const payload = {
        username: 'łukasz',
    }

    console.log(payload) // -> {username: "łukasz"}

    let frontToken = Buffer.from(JSON.stringify(payload)).toString('base64')

    console.log(frontToken) // -> eyJ1c2VybmFtZSI6IsWCdWthc3oifQ==

    let tokenInfo = JSON.parse(atob(frontToken))

    console.log(tokenInfo)  // -> {username: "łukasz"}

So the bug is within this code itself.. nice

I will try to figure that out as well

@User the error is in how

atob

is used in the frontend. It should be changed to this:

function b64DecodeUnicode(str) {
    return decodeURIComponent(Array.prototype.map.call(atob(str), function (c) {
        return '%' + ('00' + c.charCodeAt(0).toString(16)).slice(-2)
    }).join(''))
}

let tokenInfo = JSON.parse(b64DecodeUnicode(frontToken))

console.log(tokenInfo);

I'll release a new version of the supertokens-website repo with the above change, and you can update your dependency.. it should work fine then.