Woot! android application only; browsers work fine.
Samsung S21 FE
It is the same Daily Deal category location every day. Everything else works fine.
Click on this and only this…
Immediately returns this…
Woot! android application only; browsers work fine.
Samsung S21 FE
It is the same Daily Deal category location every day. Everything else works fine.
Click on this and only this…
That’s weird. I just clicked on that & had no problem
& I clicked on the skincare category yesterday & had no issues. Past few weeks I’ve just been getting a lag on the loading altogether, but I chalked it up to having an older phone. I’m on android 13 with a moto g stylus 5G (2022) using the app.
Same as kevinahalleck, it is on the fragrances today. I also am aware it is not happening to everyone as family and friends aren’t getting it on there app. I use a Samsung s22
I’m having the same issues, also on a Samsung phone using the app. Today it’s the pantry clear out deals that won’t load. It’s one deals section usually a day for me that fails, especially skincare and beauty deals. I’ve cleared cookies and even the cache for all apps trying to fix it. It started about 10 days ago. Please let me know if there’s a way to fix it.
Works fine on my pixel 5, so maybe a Samsung issue?
Samsung definitely seems to be a common thread.
I am having the same issue again today.
I had the issue again tonight. Closed the app, cleared cache, still not working. Closed the app, cleared cache and deleted app data and everything works fine now. Maybe there is some corrupted data in the app files.
Hello all. Thanks to the screen shots, our developer thinks he’s figured out the issue.
UPDATE: Fix has been pushed out. Make sure you close and restart your app a couple times to get the update. Let me know if there’s still an issue.
Thank you! So far, so good!
![]()
The identical issue has returned as of today’s offers and homepage format on the Android application.
As before, it’s only the second from last Daily Deal (Sweet Tooth Paradise).
I have tried each of the normal procedures and nothing helps. I am uncertain if someone reverted the recent changes that eliminated the issue or what happened, but whatever was done no longer works for my situation.
![]()
Drat. I’ll let the devs know.

In the last two days I have suddenly started getting the same “400 error” whenever I try to access the payment process in the Woot app for Android.
I can place items in my cart, but when I try to pay for them I immediately get the error. So far, as a work around, I need to exit the application and complete the payment process in a browser via the website. The only change that I have made to my Amazon account in the past few days is to add an additional payment method and it is not the default method. I am at a loss to explain what is causing this error or how to correct it.
Thank you for your continued support and assistance
Hi. The dev team is asking for more information on this latest error for the payment process and some screen shots to help them understand it. You can send these to me via private message if you prefer.
They think it may be a different issue.
Early this a.m., I started getting the 400 error in the payment process.
Cleared cache, rebooted phone a couple times. Still getting error.
Pixel 5. Android.
I’ll add a screen shot.
Fixed it! Logged out and back in.
My pup can get a new toy.
And no longer panicked over not being able to pay during mini woot-off, omg, wtf.
Is anyone else having issues checking out on the app? It says error 400 header too large or cache
Yes, it’s an issue that has also popped up for me in the past few days. As with the previously mentioned issue, I have no such issue using a browser.
This is now the second “400” error that I am experiencing with the Woot! app for Android on my Samsung Galaxy S21 FE.
Could you both please try removing the woot app and reinstalling it? TY.
New discovery with these errors. I’m getting the 400 error when selecting the category in the same space as mentioned above only when I’m logged in. When I log out, I can browse to the category with no issues.
As for the mention of those getting the error when checking out, I’ve started getting these errors when I’ve freshly open the app and was previously logged in. When I log off and log back in, I am able to check out with no issues.
Also as others have mentioned, I’m on an Samsung device.