Closed bluiska closed 6 years ago
So the weird thing is that I left the thing for a while and for the fun of it I tried to see if it worked and it did! Somehow it took Amazon a while to actually update the invocation name... weird. Why could this have happened?
you can change the invocation name in developer.amazon.com
Edit skill under that you can see invocation and change
Thank you @avrpayyyur for helping - looks like the problem is solved. Closing this issue.
I'm having the same issue. I've changed my invocation name, saved, built. minutes after getting the build complete message, it's still responding to the old invocation name and not the new. I think there are propagation issues with the build process. Done doesn't mean done.
When you change the invocation name, you need also to disable and reenable the skill on your account. Just turn off the test switch and turn it on again
--Seb
Sent from a smartphone. Please, accept apologies for brevity and typos.
On 30 Aug 2018, at 17:01, kfred notifications@github.com wrote:
I'm having the same issue. I've changed my invocation name, saved, built. minutes after getting the build complete message, it's still responding to the old invocation name and not the new. I think there are propagation issues with the build process. Done doesn't mean done.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
When you change the invocation name, you need also to disable and reenable the skill on your account. Just turn off the test switch and turn it on again
@sebsto Thanks it solved the problem.
When you change the invocation name, you need also to disable and reenable the skill on your account. Just turn off the test switch and turn it on again
That worked for me. I would call this a bug, as there is no indication anywhere (eg, when changing the invocation name) that this is required.
Definitely it's a bug. spent two hour for me to find what's wrong.
Bug (or lack of an informational message). I spent a good 45min trying to figure this out too.
Can confirm this issue still exists.
When you change the invocation name, you need also to disable and reenable the skill on your account. Just turn off the test switch and turn it on again
That worked for me. I would call this a bug, as there is no indication anywhere (eg, when changing the invocation name) that this is required.
Where do I do this at? I'm having the same issue
you can do that either in the Alexa developer console (developer.amazon.com) in the Test tab. Or on the Alexa App (on mobile or alexa.amazon.com) in the Skills section.
can anyone tell me about this issue https://github.com/alexa/skill-sample-nodejs-audio-player/issues/149#issue-441232779
did anyone bother to add the "disable/enable again" instruction into some documentation somewhere when this issue was "resolved"?
Hi! I tried everything I could be I don't seem to be able to change the invocation name so I could use the template for my own skill. I have changed every reference I could find to "audio player" to "my own name" but no matter if I re-deploy or change the name in the alexa console I can only refer to the skill by the name "audio-player". Also, is there a way to play non-HTTPS links?
Thank you!
PS: Otherwise this repo is super useful!