$request.getAccessToken() returns undefined in Google Conversational Actions

I’m submitting a…

• Bug report
• Feature request
• Documentation issue or request
• Other… Please describe:

Expected Behavior

In Google Conversational Actions…

const { GoogleAssistant } = require('jovo-platform-googleassistantconv')

after the user has successfully gone through the Account Linking Scene and linked their account, and returned to the ON_SIGN_IN handler, calling this.$request.getAccessToken() should return the access token.

Current Behavior

The function GoogleAction.$request.getAccessToken() is defined, yet it never returns the token, despite the account being linked.

console.log(`this.constructor: '${this.constructor.name}'`)
console.log(`typeof this.$request.getAccessToken: '${typeof this.$request.getAccessToken}'`)
console.log(`this.$request.getAccessToken(): '${this.$request.getAccessToken()}'`)

Error log

This is the output of the code above:

this.constructor: 'GoogleAction'
typeof this.$request.getAccessToken: 'function'
this.$request.getAccessToken(): 'undefined'

Your Environment

$ jovo -v

Jovo CLI Version: 3.2.1

Jovo packages of current project:
  jovo-core: 3.3.1
  jovo-db-filedb: 3.3.1
  jovo-framework: 3.3.1
  jovo-platform-alexa: 3.3.1
  jovo-platform-googleassistantconv: 3.3.2
  jovo-plugin-debugger: 3.3.2

[NLueg]

I’m having the same Issue. I tried every getter for the access token without any success. I managed to get the token with the following code:

export function getAccessToken(jovo: Jovo): string | undefined {
  if (jovo.$request && jovo.isAlexaSkill()) {
    return jovo.$request.getAccessToken();
  }

  // TODO: Temporary hack to receive the access-token
  if (jovo.isGoogleAction()) {
    const headers = jovo.$googleAction.$user.conversationalAction.$host.headers;
    const accessTokenWithBearer = headers['Authorization'] || headers['authorization'];
    return accessTokenWithBearer?.replace("Bearer ", "");
  }

  return undefined;
}

But I think that the problem is inside the ConversationalActionRequest. It seems to be expected, that the access token is inside the user but this is not the case for me too.

[aswetlow]

I close this issue due to inactivity.