You will need to use the website or an Alexa app in order to finish the setup process.Īfter getting numerous reports from numerous customers, we made the decision to look into the situation and developed a series of fixes that worked for the majority of our consumers. Although these gadgets are quite important in our daily lives, setting one up can be very difficult. Any Alexa-enabled devices, such as the Amazon Echo, Echo Dot, and Echo Spot, may fall under this category. It would also be great if you can let us know of any feedback, feature requests or issues around the extension.Nothing is more frustrating and annoying than having your Alexa app not working while the Alexa devices are being set up. Please let us know if you are still facing problems. I am going ahead and closing this and #54 issue. The create skill view from the extension should work flawlessly for you now. If i ever have to create a new skill i guess i will have to create it first in dev console then open it up in VS, we hope the latest extension release fixes this for you. As observed, the recent extension release v2.2.0 should have these issues fixed. Anyone can view the toolkit updates view again, in the extension, by running the Alexa: Show Toolkit Update notes command in the vscode command fixed the scripts and released them recently.
As a small token of appreciation, we added your github user names in our Thank you section in the toolkit updates view. Special thanks to & to debug and help us resolve the issue. I used git checkout dev in the example above because that seems to be the branch that is associated with the code you actually edit in the Alexa Developer sorry for the late response and thanks for keeping this thread super active and updated on the progress. I'm hoping there is a quicker, easier resolution found soon.ĮDIT: You should probably use git checkout master and git checkout prod as well. I figured if anyone on the internet is as visual a learner as I am, this should be helpful. You will now see files populate in your workspace: Type the command git checkout dev and press enter. Type the command git fetch and press enter.Now navigate back to VSCode and make sure to open the folder with your skill (if its not already opened) in your workspace.I managed to fix it by simply adding quotes around $" | tr -d ' ' | sed -n $configOp | sed 's/".*//') Reason: Git folder setup failed for), git fetch also did not work this time. However, it fails later with the same issue I mentioned ( Skill creation failed. Downgrading to 1.49.3 does make Download and edit skill button work.
0 kommentar(er)
