unable to link Alexa skill with my mobile application in development/testing mode
Rakesh baloda
asked 10 months ago

Question

[https://repost.aws/questions/QUlK6wP8dVRUCF-XNwwMCIJw/unable-to-link-alexa-skill-with-my-mobile-application-in-development-testing-mode#ANlAMb2IAdR--_tcd56LxxhQ]()

**1. Content-Type Header:**
- I am able to see the Content-Type header in the response, and it is being returned as:

> Content-Type => application/json; charset=utf-8

**2. CORS Settings:**
- Here are the CORS settings I am using in my backend:

```
res.header("Access-Control-Allow-Origin", "*");
res.header("Access-Control-Allow-Methods", "GET,HEAD,OPTIONS,POST,PUT");
res.header(
  "Access-Control-Allow-Headers",
  "Origin, X-Requested-With, contentType, Content-Type, Accept, Authorization"
);
next();
```

**3. Public Accessibility:**
- I have made my API publicly accessible, so it can be reached from external clients without network restrictions.

**4. HTTP Status Codes:**
- I am handling HTTP status codes properly in my API. For example, whenever there is an error, I return the appropriate status code along with the response.

> return res.status(400).json(response);

- Even after implementing all of the above, I am still facing the issue “Unable to link the skill at this time” during the account linking process.

- Can anyone suggest what else I might be missing or what additional configuration is required on the AWS side?

re:Post Agent · Answer

Based on your description, you're experiencing the "Unable to link the skill at this time" error when trying to link your Alexa skill with your mobile application in development mode, despite having implemented several best practices.

Here are some potential solutions and areas to check:

1. **Token Response Structure**: Ensure your OAuth token response follows the exact format expected by Alexa:
```json
{
"access_token": "your_access_token",
"refresh_token": "your_refresh_token",
"token_type": "Bearer",
"expires_in": 3600
}
```
Verify there are no extra spaces, special characters, or formatting issues in the actual response.

2. **Authentication Configuration**: Double-check that your Alexa skill's account linking configuration matches exactly with your authentication service settings, including redirect URIs, client IDs, and client secrets.

3. **CORS Settings**: While your CORS headers look good, make sure they're being applied to the specific endpoints that Alexa is calling. Sometimes middleware might not be applied to all routes as expected.

4. **Token Validation**: If you're generating tokens using crypto libraries, ensure they meet any specific format requirements. The access token and refresh token should be properly formatted strings.

5. **Skill Configuration**: Verify that all settings in the Alexa Developer Console for account linking are correctly configured, including any required permissions.

6. **Server Logs**: Check your server logs during the account linking attempt to see if there are any specific errors being returned that could provide more insight into what's failing.

7. **Testing Environment**: Ensure that your development endpoints are publicly accessible and that all security certificates are valid.

8. **Browser Issues**: Try clearing your browser cache and cookies, using incognito/private mode, or trying a different browser or network connection.

If the issue persists, you might want to verify the complete flow outside of the Alexa environment first to ensure your authentication flow works end-to-end.  
**Sources**  
[Unable to link Alexa skill with my mobile application in AWS (Dev mode testing) | AWS re:Post](https://repost.aws/questions/QUjeBmts_kS-2LLtrsGjMM2Q/unable-to-link-alexa-skill-with-my-mobile-application-in-aws-dev-mode-testing)  
[Unable to link Alexa skill with my mobile application in AWS (Dev mode testing) | AWS re:Post](https://repost.aws/questions/QUCawiNA1GR26Q1_vwPpizTg/unable-to-link-alexa-skill-with-my-mobile-application-in-aws-dev-mode-testing)

unable to link Alexa skill with my mobile application in development/testing mode

Add your answer

Relevant content