"Couldn't update the settings. Check your connection"
See original GitHub issueAfter I choose the “device” and login there’s a progressdialog with “Linking your … account”… then I got an error: “Couldn’t update the settings. Check your connection” (Used the mock server)
POST /token 200 17.212 ms - 100
POST / 404 1.183 ms - 140
Probably the 404 reply for / ?
Issue Analytics
- State:
- Created 6 years ago
- Comments:38 (11 by maintainers)
Top Results From Across the Web
How to fix "Couldn't update the setting. Check your connection ...
How to fix " Couldn't update the setting. Check your connection " error - Google home and Phillips Hue.
Read more >"Couldn't update the setting. Check your connection" error ...
When I add the Homeseer linked service to Google Home, I immediately get the message "Couldn't update the setting. Check your connection" It ......
Read more >Fix: Windows Update Error "We Couldn't Connect to ... - Appuals
Fix: Windows Update Error “We Couldn't Connect to the Update Service” · Check your Internet · Use Mobile Data · Change your DNS...
Read more >We Couldn't Connect to the Update Service: Solved
1. Verify your Internet connection · 2. Make sure you have enough disk space · 3. Run the Windows Update Troubleshooter · 4....
Read more >We couldn't connect to the update service in Windows 11/10
To fix We couldn't connect to the update service error, do the following: Run Windows Update troubleshooter. Run Internet Connections troubleshooter.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here is the logcat log, sorry if any personal trash was mixed inside and great thanks for the help.
i resolved my different login issues with this bug fix #108, maybe it can help someone else