Not sure where you're all located but I'm in the UK and have not had any issues....yet! (kiss of death)
I've had occasional errors in the past and a device become unresponsive a couple of times, but all ok since 2.5
Possibly region specific?
There are people on the SmartThings Community forums that are in the UK with issues.
I’m also UK and it’s down for me 
It is likely just a matter of a bit of time before everyone's cookies expire...
I'm not sure why the cookies are now failing but if you're looking for a short term fix, you can manually enter the cookie and that seemed to fix it for me.
- Open your echo speaks app
- Click "Login Service Settings"
- Click "Heroku App Settings"
- In the Heroku pop-up, click "Open App" (at top)
- In the new page that is opened, there should be a button to manually enter a cookie.
- Follow steps here to get that info and enter it.
Mine seems to be working ok after that.
1 Like
wow... i try to take a couple days off work and relax with the family and shit hits the fan 
i need everyone to relax and let me try to catch up...
6 Likes
i’m pretty sure this is related to the UK only for the moment. i’m in the US and token refresh is working for me.
I didn’t write the module used for the cookie collection and refresh. I have worked with Apollon77 on a couple issues in the past so we have a decent rapport...
the module used to handle the logon cookie process is GitHub - Apollon77/alexa-cookie: Library to generate a cookie including a csrf for alexa remote
I just modified to work with UI and run under heroku.
Token refresh is not working for me and I use amazon.com
All I get is loop to get a new token using the Heroku login screen. Try a manual cookie doesn't work either.
1 Like
I’m in the US too and it failed for me.
Agreed with posters above. Both manual + token refresh do not function for me; US based.
Definitely not working for me and I’m in the US.
Neither normal login/refresh nor manual token work.
Just tried mine again and not working. I'm in US.
I am down in the US too.....waiting patiently for a fix. 
app:20592019-06-20 08:07:04.687 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)
app:20592019-06-20 08:07:04.685 am tracecookieRefreshResp...
app:20592019-06-20 08:06:46.048 am debugDevice Data Received and Updated for (2) Alexa Devices | Took: (1987ms) | Last Refreshed: (10.0 minutes)
app:20592019-06-20 08:06:34.780 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null
app:20592019-06-20 08:06:34.578 am tracegetCookieData() Request Received...
app:20592019-06-20 08:06:34.439 am debugwakeUpServer Completed... | Process Time: (308ms)
app:20592019-06-20 08:06:34.439 am tracewakeUpServerResp...
app:20592019-06-20 08:02:04.695 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)
app:20592019-06-20 08:02:04.688 am tracecookieRefreshResp...
app:20592019-06-20 08:01:34.784 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null
app:20592019-06-20 08:01:34.572 am tracegetCookieData() Request Received...
app:20592019-06-20 08:01:34.369 am debugwakeUpServer Completed... | Process Time: (278ms)
app:20592019-06-20 08:01:34.369 am tracewakeUpServerResp...
app:20592019-06-20 07:57:04.666 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)
app:20592019-06-20 07:57:04.663 am tracecookieRefreshResp...
app:20592019-06-20 07:56:46.044 am debugDevice Data Received and Updated for (2) Alexa Devices | Took: (1992ms) | Last Refreshed: (10.0 minutes)
app:20592019-06-20 07:56:34.818 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null
app:20592019-06-20 07:56:34.589 am tracegetCookieData() Request Received...
app:20592019-06-20 07:56:34.400 am debugwakeUpServer Completed... | Process Time: (264ms)
app:20592019-06-20 07:56:34.400 am tracewakeUpServerResp...
app:20592019-06-20 07:52:04.743 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)
app:20592019-06-20 07:52:04.736 am tracecookieRefreshResp...
app:20592019-06-20 07:51:34.908 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null
In US. Manual cookie entry via Heroku worked for me. Needed to input both cookie and csrf values.
What method did you use to get the cookie for manual entry?
Did you have to remove double quotes or add anything to the cookie?
Update: Disregard. The manual cookie and CSRF worked.
Update 2: So the manual entry of the cookie and CSRF was accepted and the app shows a cookie date of today, but my Echo devices are not actually announcing anything.
1 Like
I followed the steps of @rvrolyk and entered the cookie manually. What is the CSRF and where do we get it? Also, how will I know if it is working?
After you initially copy the cookie from the browser, paste it into a text editor. The CSRF should be one of the items listed. I missed it at first.
As I posted above, even though everything seemed OK in Heroku with the manual entry and Echo Speaks shows a cookie in the app on HE, my Echo Dots are not announcing.
