11-20-2017 06:40 AM - edited 11-20-2017 06:43 AM
I've tried setting up the Ask Act Alexa skill, and I'm getting this error: "Aquire Alexa Token Error: BadRequest". This same error occurs with 2 different databases.
I'm using Alexa App client version 1.24.3086.0; Bridge version 2.2.317.13 on a Galaxy S8 with Android version 7.0. Each Act database I've tested is on a different server running Act! v20. Both are running Version 184.108.40.206, Update 4
11-20-2017 11:54 AM
Amazon has not made its Alexa service compatible with Samsung products
Best to use an Amazon device, such as Amazon Echo
11-20-2017 12:27 PM
I'm sorry, I wasn't clear in my previous post. I am using the Alexa App on my phone to add and configure the skill, but not to use it. I have an Echo Show.
After receiving your response, I went online to my Amazon.com account, searched/found the skill and attempted to link my account. I received the same error.
11-21-2017 01:09 AM
11-21-2017 08:18 AM
Yes, I have a password.
Yes, I'm using the proper case.
Yes, these are the same credentials that I use for Act! companion with no problem.
And, this is happening with more than 1 set of credentials. I have also tried it with credentials for a database located on a different server, and I'm getting the same results.
11-21-2017 08:36 AM
11-21-2017 04:17 PM
This may sound odd, but can you ensure the Act! password you are using is longer than 6 characters. I had this issue from multiple databases in setting up an Echo Show today, and it resolved it for me.
Let me know if this helps and we'll ensure it's made clear on the setup steps.
11-22-2017 07:45 AM
For one of my test cases, the password is 9 characters, and for the other it's only 5. I will try changing the one that is 5 to see if that makes it work. Do you have recommendations on using lower case/upper case / symbols / numbers in the password that might help? For the password that is 9 characters I don't have any upper case or symbols. Do you think that could be the issue?
11-27-2017 08:08 AM
After 2 months of try to beta test and hours of tech support from inside people at Swiftpage, not once did anyone ask if my password was at least 6 characters. Incidentally, it isn't...or wasn't...for nearly 2 months I've been getting the aquire token error...with the misspelling that no one cares to correct. I saw this this morning, changed my password to more than 5 characters, which it was, and now it works.