I succeeded first certification on November 3, 2017.
After a little modification of the interaction model, I submit to re-certification on December 21, 2017.
Re-certification failed, and a answer came.
But I do not understand the answer, so I post this question.
The answer is:
The skill must deliver a link account card to the Home section when launched by users who have not yet linked an account. Additionally, the skill must inform users that the link account card was delivered to home section and to complete the functionality they should complete account linking. Steps To Reproduce: User: "Alexa, launch miro" Skill: "With the Miro humidifier skill, you can turn on your humidifier to the desired high, medium, low setting, and turn the nightlight on or off. The Miro humidifier skill allows for remote voice-control of your humidifier." Please refer to test case 3.4 in the Functional Testing section of the Submission Checklist for more information. The skill is not consistently launching when attempting various supported launch phrases. This issue is likely resulting from (invocation name issue(s) identified). Steps To Reproduce: User: "Alexa, ask Miro to turn on the humidifier" Please note that the skill's request fails to reach the end point. Please see our documentation on creating an invocation name for your skill that will work to consistently launch the skill. Additionally please refer to our documentation on the voice interface for creating the best user experience.
My skill's invocation name is 'miro'.
When LaunchRequest comes to an endpoint, it returns a brief introduction.
also succeeded to first certification with this case.
However, one of the reasons for this re-certification failure is that when user say "launch miro", I have not processed the link account.
Currently, my skills do not need to be link to account because only a brief introduction is shown when launching.
Intent that need to be linked account will send a link account card to the home section with a message stating that an account link is required.
I am looking again at the Test case 3.4 section of Functional Testing in the Submission Checklist document to see if the policy of the account linking has changed.
But intent that do not need to be linked account in the document are still instructed to works correctly.
And another reason for this re-certification failure is that the skill has not reached at the endpoint.(Currently my endpoint is a lambda function.)
The solution suggested in the answer is to refer to the documentation to create a invocation name.
But I know that the invocation name of the skill that succeeded in first certification is not changeable. (As a result of direct examination, it is impossible to changed.)
In addition, when I test the text directly on the Alexa console, I can see that the invocation name does not reach the endpoint when it is 'Miro', and it reach at the endpoint when it is 'miro'.
This is the skill that has already been successfully first certified, so I do not know how to fix it if it fails.
I Ask for advice or help with these issues.