TypeError when calling getAccessTokenSilently cache-only while no user is logged in

[JasonWeinzierl]

Checklist

• The issue can be reproduced in the auth0-angular sample app (or N/A).
• I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

The following causes a TypeError when no user is logged in:

    this.auth.getAccessTokenSilently({ cacheMode: 'cache-only' }).subscribe();

I would expect either a more intentional error to be thrown, or change the type annotations to indicate string | undefined and return undefined to indicate no access token is available.

Reproduction

1. Add the above line to HomeComponent' constructor in the auth0-angular sample app
2. Launch the app and don't log in
3. See TypeError logged in the browser console

Additional context

home.component.ts:11 ERROR TypeError: Cannot read properties of undefined (reading 'access_token')
    at TapSubscriber._tapNext (auth0-auth0-angular.mjs:396:137)
    at TapSubscriber._next (tap.js:40:27)
    at TapSubscriber.next (Subscriber.js:49:18)
    at MergeMapSubscriber.notifyNext (mergeMap.js:70:26)
    at SimpleInnerSubscriber._next (innerSubscribe.js:10:21)
    at SimpleInnerSubscriber.next (Subscriber.js:49:18)
    at subscribeToPromise.js:5:24
    at _ZoneDelegate.invoke (zone.js:368:26)
    at Object.onInvoke (core.mjs:26249:33)
    at _ZoneDelegate.invoke (zone.js:367:52)

auth0-angular version

2.2.0

Angular version

16.1.2

Which browsers have you tested in?

Chrome, Firefox

[JasonWeinzierl]

Probably caused by typeof token === 'string' returning false when it's undefined, and so token.access_token blows up

[frederikprijck]

Thanks for reporting this, I fixed it in #458

[frederikprijck]

Fixed and released in v2.2.1