New behavior as of today:
"request": { "type": "IntentRequest", "requestId": "amzn1.echo-api.request.e58a65ba-0aa0-46b9-b780-5875b70cad02", "locale": "en-US", "timestamp": "2021-09-22T21:08:09Z", "intent": { "name": "LatestEpisodeIntent", "confirmationStatus": "NONE" } }
but what’s reaching my jovo app.js
is a call to NEW_USER()
rather than LatestEpisodeIntent()
. In fact, I’m getting sent to NEW_USER()
even in response to
"request": { "type": "SessionEndedRequest", "requestId": "amzn1.echo-api.request.7a0173ca-724b-4119-acc0-6514fe340780", "timestamp": "2021-09-22T21:36:15Z", "locale": "en-US", "reason": "EXCEEDED_MAX_REPROMPTS" }
This also happens when I feed requests to it via the Developer Console’s test page.
I tried rebuilding the development directory – did a “jovo new test
”, copied my source files in, added the date-fns
package via npm
, and did “jovo run
” from there without any other npm
update requests. This copy is working in the debugger (more or less, subject to the debugger’s limitations), but when I connect my account to it as a beta user, requests via the Echo are all winding up in NEW_USER
.
I am very confused, and rather frustrated…
ANY assistance in figuring out what’s going on would be much more than welcome. Stupid questions welcome.
(Of course this misbehavior started on the first day when I was going to have real beta users. Murphy’s law.)
(And no, fixing my deploy problem did not resolve this one.)