My Alexa app keeps glitching, not recognizing devices, and sometimes won’t load skills or routines I’ve set up. I’ve tried basic troubleshooting like reinstalling the app and restarting my phone, but nothing has worked so far. I need advice on what else I can do to fix the Alexa app, or if there are any advanced settings or known bugs I should be aware of to get it working normally again.
Seen this a bunch with Alexa lately. The app glitches more than the speakers do. Here is what usually helps, in order, so you do not waste more time.
- Check Amazon and account basics
- Open amazon.com in a browser.
- Make sure you are logged in with the exact same account as the Alexa app.
- If you use multiple Amazon regions, log out on all, then log back in to one region only. Region mismatches cause devices and skills to vanish or act weird.
- Reset the Alexa app data, not only reinstall
Reinstall often keeps cached junk.
Try this instead:
On Android
- Settings
- Apps
- Alexa
- Force stop
- Storage
- Clear cache
- Clear data
- Reopen Alexa and sign in again
On iPhone
- Delete Alexa app
- Power off the phone for 30 seconds
- Turn it on
- Reinstall Alexa
- Sign in again
- Check your phone network and DNS
Alexa app depends on stable HTTPS calls. If your phone uses a VPN, ad blocker, or funky DNS, stuff breaks.
- Disable VPN and private DNS for a bit.
- Turn off Wi Fi. Try on mobile data.
- If it works fine on mobile data, your home network or router blocks some Amazon domains.
- Sync devices from the app
Sometimes devices exist in the cloud but the app fails to refresh.
- Open Alexa app
- Devices tab
- Top right menu
- “Discover devices” or “Scan for devices”
- Wait a minute, then check if your devices show correctly.
- Remove and re add one problem device
Pick one device that fails a lot and test it as a sample.
- In the Alexa app, remove that device.
- Factory reset that device, following its manual.
- Put it in pairing mode.
- Add it again through the Alexa app.
If that device works fine after this, repeat for the others that misbehave.
- Check skill and region mismatch
Some skills only work in certain countries. If your Amazon account country and your phone region or app store region do not match, skills fail to load or routines break.
- In a browser go to alexa.amazon.com or alexa.amazon.co.uk etc.
- Check the skills section there. Remove and re enable the ones you use.
- Confirm your country settings under “Content and Devices” on Amazon.
- Fix routines that hang or never run
Routines often break when:
- A device it controls was renamed.
- A skill used in the routine got removed or needs relink.
Steps: - In the Alexa app, open each routine.
- Look for any step marked with a warning or missing device.
- Re select the device or delete that step.
- Disable the routine, wait 10 seconds, then enable it again.
- Log out of all other devices
If you share your account, conflicting sessions cause weird behavior.
- Log out of Alexa app on tablets and spare phones.
- Log out of Alexa on Fire TV and other places you do not use often.
- Log out of the app on your phone, then log in again.
- Quick Echo device checks
If the speakers respond but the app is broken, still worth a check.
- Ask “Alexa, what Wi Fi network are you on” to confirm.
- Say “Alexa, update your software”.
If she says up to date and works fine by voice, your problem lives mostly in the app or account side.
- Narrow down what exactly fails
From what you wrote, there are three separate layers that glitch:
- Device discovery and control
- Skills
- Routines
Try this checklist and see which step fails: - Disable then re enable one important skill. Test it.
- Create a brand new simple routine: “When I say ‘test routine’ turn on living room light”.
- If the new routine works but old ones do not, they are corrupted. Rebuild the key ones from scratch.
- If skills refuse to stay linked, your account or permissions are off. Go to the skill website and relink from there if possible.
- Test from a browser, not only the phone app
Go to alexa.amazon.com in a desktop browser.
- If devices and routines look normal there, the mobile app install is messed up.
- If you see the same broken state, the issue is in your Amazon backend account, not your phone.
- When nothing works, do a full account cleanup
This is annoying but often fixes persistent weirdness.
- Screenshot your routines and device names first.
- In the Alexa app and browser, remove old devices you no longer use.
- Disable skills you no longer need.
- Power cycle your router.
- Then re add only your core devices and rebuild a couple of key routines.
If stuff stabilizes with a simpler setup, you know some old ghost device or skill link was breaking things.
If you post your phone type, Alexa app version, and whether the glitches happen on Wi Fi or mobile data, people here can guess more precisely where it is going wrong.
Yeah, Alexa’s app has been on its clown arc lately. Since you already did the basic “reinstall and reboot” and @chasseurdetoiles covered most of the normal checklist, here are some other angles that hit different parts of the stack instead of repeating all that:
- Check if it’s account-wide or device-specific
- Log into alexa.amazon.com on a desktop browser.
- Try creating a tiny test routine there and see if it runs.
- If the routine works from the browser but not from the phone app, the app layer is the problem.
- If it fails from both, your account / cloud state is borked, not your phone.
- Try a second phone or tablet
Borrow another phone if you can. Install the Alexa app, log in with your same account.
- If everything looks normal and loads fine there, your original phone has some weird interaction: battery saver, network stack, or some background restriction killing the app.
- On Android especially: turn off battery optimization for Alexa, allow “unrestricted” background data, and make sure it’s allowed to run in background.
- Check for partial outages and throttling
Amazon quietly breaks stuff sometimes.
- In the app, go to “Settings → Help & Feedback → Contact Us” and see if there’s any banner about service issues.
- Also watch if problems happen mostly at certain times of day. If routines time out at “busy” hours but work later, it can be backend throttling and your account is just unlucky in the queue.
- Look for “ghost” homes and locations
The app sometimes creates or keeps old “homes” and randomly dumps devices there.
- In the app, go to Devices → top menu → check if there’s more than one Home / Group / Location.
- If you see an extra home/location you never use, move all live devices to the main one and then delete the empty ghost home.
This actually fixes a ton of “devices not recognized” and “routine can’t find that light” issues.
- Strip out one integration layer at a time
If you use stuff like SmartThings, Hue, TP Link, etc, pick one and temporarily disconnect it.
- Disable that specific skill.
- Wait a couple minutes, force close the Alexa app, reopen.
- See if the app becomes less glitchy with one large integration removed.
Some of these skills can stall the device list or routine loading for everything when they misbehave. @chasseurdetoiles mentioned region stuff, but even within the same region a flaky cloud integration can poison the well.
- IPv6 and router weirdness
This is more niche, but it bites a lot of people:
- On your router, temporarily disable IPv6 (if enabled) and reboot the router.
- Connect phone again and test the Alexa app.
Some Amazon endpoints over IPv6 behave differently and the app just sort of… half loads.
- Routine “rehydration” trick
For routines that just refuse to fire even though they look valid:
- Edit the routine trigger to something else, save.
- Edit it back to the original trigger, save again.
This forces it to re-save in the backend. Sometimes works better than just toggling the routine off/on like suggested earlier.
- Check for data corruption on Android specifically
If you are on Android and used older versions of the Alexa app, sometimes Play Services / WebView mess with embedded login pages and skills panes.
- Update “Android System WebView” and Chrome to latest.
- Then try loading skills again.
The app UI is basically a wrapper around web content. If WebView is messed up, the skills/routines pages half-load or freeze.
- When it’s clearly the account
If you see the same broken devices and busted routines on:
- Your phone
- Another phone
- Browser
then it is 99% an account state issue on Amazon’s side. The nuclear but effective path is: - Screenshot everything: device names, groups, routines.
- In a browser, delete dead / offline / duplicate devices, especially super old ones.
- Disable skills you no longer use, especially ones that show as “linked” but don’t actually respond.
- Wait a bit, then re-discover devices and very slowly rebuild only your 2 or 3 key routines first.
If those work when the account is “clean,” you know old junk data was breaking it.
- Contact support the annoying but specific way
When you talk to support, don’t just say “my app glitches.” Tell them:
- “Devices list fails to load / times out.”
- “Routines page won’t open / blank.”
- “Skills show as enabled but fail to load configuration.”
and specifically mention you tested: - different phone
- browser
- mobile data vs WiFi
Ask them to check for “account sync inconsistencies” or “orphaned devices and routines” on your Alexa account. That sometimes gets them to escalate beyond the usual script.
If you can post what phone model, OS version, and whether this behaves differently on mobile data vs WiFi, that narrows it down a lot. Right now it sounds less like a single broken device and more like your account or network confusing the Alexa backend.
Couple of angles that haven’t really been hit yet, focusing on how the app behaves over time rather than just one‑off fixes.
- Look for a pattern in when it glitches
Instead of poking randomly, watch it for a day:
- Does it get worse after you’ve had the app open for a while? That usually points to the in‑app web views leaking memory.
- Does it misbehave mainly after you switch networks (home Wi‑Fi to mobile, work Wi‑Fi to home)? If yes, the session cookies inside the app often get confused. In that case: fully log out of the Alexa app, kill it from recents, then log back in every time you swap networks for a quick test.
If log‑out/log‑in temporarily stabilizes it, you are looking at session handling issues on Amazon’s side, not “your phone is bad.”
- Trim how many things Alexa has to juggle
This one I slightly disagree on with the “just clean up old stuff at the end.” In my experience, the app starts acting flaky long before you hit truly ridiculous device counts. Do an early, aggressive declutter test:
- Temporarily disable all non‑critical skills (especially smart home hubs, energy monitors, obscure cloud connectors).
- Turn off only 1 or 2 core routines, then create one brand new test routine and see if it consistently shows up and runs.
If the app suddenly becomes snappier once the account is simpler, that tells you it is choking on the complexity, not necessarily any single bad device.
- Watch for race conditions between speakers and the app
If your Echo devices respond instantly by voice while the app is “loading” or spinning:
- Use voice to tweak something that should reflect in the app, like “Alexa, create a routine called ‘voice test’ that says ‘hello’.”
- Then see how long that routine takes to appear in the app.
If the delay is big, the backend is fine and the sync channel to your app is slow. In that case, trying more reinstalls is wasted effort. Better to test from a browser plus a second phone, like @himmelsjager suggested, and push Amazon support on “account sync delay” rather than generic app bugs.
- Competing app behavior and background killers
Android in particular: if you run a bunch of assistant or automation apps (Google Home, SmartThings, vendor apps like Hue, TP‑Link, etc), the OS sometimes gets aggressive with memory. Instead of just disabling battery optimization for Alexa, try the reverse:
- Temporarily uninstall or log out of non‑critical smart‑home apps for a day.
- See if Alexa becomes stable when it is the “main” control surface.
If yes, it is less of a pure Alexa bug and more about how your phone is juggling background processes.
- When to stop tweaking and push Amazon
Where I think both @himmelsjager and @chasseurdetoiles are a bit too optimistic is on how much end users can fix themselves. From your description already:
- You reinstalled
- You restarted the phone
- Skills and routines sometimes load, which hints at flaky backend sync
If you have: - Confirmed the same weirdness on at least one other device or in a browser
- Seen devices randomly appear/disappear or skills showing as enabled but not loading
then it is time to stop burning hours on local tweaks and open a support ticket with a very specific list: - Exact time and time zone when a routine failed
- Name of the routine
- Name of at least one device that failed to show in the app
Then ask them to “check for account sync inconsistencies or corrupted device entries” on your Alexa account. That phrasing usually gets your case escalated a bit faster than “my app is glitchy.”
Pros of pushing support early:
- They can see logs and backend errors you never will.
- If it is an account‑state problem, nothing on your phone will fully fix it.
Cons:
- It is slow and you may need multiple contacts.
- First‑level support will still walk you through some basic steps you already did.
As for competitors, both @himmelsjager and @chasseurdetoiles already laid out very solid front‑line troubleshooting paths. I would treat their posts as the structured checklists and use the points above when you want to decide whether to keep tinkering locally or escalate this as an account‑side problem instead of an app‑only glitch.