When following the A Path, the local application will crash after some period of inactivity (< 2hrs.) The error jwt not active implies an issue with the auth token, but after viewing the token in the Teams browser app it is still valid and has not expired.
Actions taken to attempt to fix:
- Cleared cookies and restarted app
- Restarted browser (including InPrivate) and restarted app
- Restarted ngrok and restarted app
- Restart computer and restart ngrok and application
Only restarting the computer fixes the issue, all other actions had no effect.
This is the error thrown:
Error validating access token: jwt not active
Error in /api/validateAadLogin handling: undefined
node:internal/errors:477
ErrorCaptureStackTrace(err);
^
RangeError [ERR_HTTP_INVALID_STATUS_CODE]: Invalid status code: undefined
at new NodeError (node:internal/errors:388:5)
at ServerResponse.writeHead (node:_http_server:280:11)
at ServerResponse._implicitHeader (node:_http_server:271:8)
at write_ (node:_http_outgoing:826:9)
at ServerResponse.end (node:_http_outgoing:934:5)
at ServerResponse.send (/home/rmcintyre/scratch/A01-begin-app/node_modules/express/lib/response.js:232:10)
at ServerResponse.json (/home/rmcintyre/scratch/A01-begin-app/node_modules/express/lib/response.js:278:15)
at file:///home/rmcintyre/scratch/A01-begin-app/server/identityService.js:24:38
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
code: 'ERR_HTTP_INVALID_STATUS_CODE'
}
Node.js v18.4.0
[nodemon] app crashed - waiting for file changes before starting...
When following the A Path, the local application will crash after some period of inactivity (< 2hrs.) The error
jwt not activeimplies an issue with the auth token, but after viewing the token in the Teams browser app it is still valid and has not expired.Actions taken to attempt to fix:
Only restarting the computer fixes the issue, all other actions had no effect.
This is the error thrown: