Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when token is null at decodeToken (Cannot read property 'split' of null)

See original GitHub issue

Calling the method isTokenExpired of JwtHelperService I got the following error:

ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'split' of null
TypeError: Cannot read property 'split' of null
    at JwtHelperService.webpackJsonp.../../../../@auth0/angular-jwt/src/jwthelper.service.js.JwtHelperService.decodeToken (jwthelper.service.js:62)
    at JwtHelperService.webpackJsonp.../../../../@auth0/angular-jwt/src/jwthelper.service.js.JwtHelperService.getTokenExpirationDate (jwthelper.service.js:75)
    at JwtHelperService.webpackJsonp.../../../../@auth0/angular-jwt/src/jwthelper.service.js.JwtHelperService.isTokenExpired (jwthelper.service.js:85)

This error occurred because the token obtained in the tokenGetter is null.

One possible solution would be to verify that the token obtained by the tokenGetter is null before attempting to split.

Thanks, Fabio.

Issue Analytics

State:
Created 6 years ago
Reactions:5
Comments:5

Top GitHub Comments

2reactions

Vuurbaardcommented, Jan 27, 2018

I’ve also ran into this when following the readme. There are currently 2 merge requests waiting that could fix this, would appreciate it if one of those could be accepted.

1reaction

jculverwellcommented, Aug 16, 2017

Yeah, I bumped into this yesterday. Had to check the token wasn’t null before passing it in. Agree this would be better dealt with in the isTokenExpired function.