Steam Confirmation Error, Trading Down

Is your Steam mobile app showing you an error and you can’t complete a trade? Many players are currently receiving the “There was a problem loading the confirmations page. Please try your request again later” message when they are trying to use Steam Authenticator for trade confirmation. It seems that Steam mobile confirmation is currently causing issues for many players. If you can’t confirm a trade as well, here’s what we know about the Steam mobile confirmation error.

Is Steam Trading Down? Steam Mobile Confirmation Error

On Wednesday, 20th of July, a number of players report that they are unable to confirm trades on Steam via their Steam mobile app. Steam mobile authentication is requested for numerous actions on Steam as a protection measure. That includes login into Steam, making purchases, and making trades on the Steam Community Market (SCM).

When players try to confirm a Steam trade or any other action on the market, they would receive an error saying, “There was a problem loading the confirmations page. Please try your request again later”. Another error they might get is “It looks like there is a problem with the time or timezone settings on your device. You will not be able to act on any confirmations until that problem is resolved.”

Unfortunately, there’s not much you can do at the moment. It seems that the issue is simply related to the Steam servers, and we will have to wait for Valve to fix the issue. However, just in case, you can perform a few steps. Sometimes, clearing the app’s cache can resolve issues in your Steam mobile app. Here’s how to do that:

• Open Settings on your mobile device.
• Scroll down to “Apps” and tap on it.
• Find Steam and tap on it.
• Select Storage and “Clear Cache”.

Make sure to only clear your Cache, but not the data, lest you’ll be logged out of your Steam account on your device. Another thing that some players report to work is disabling and re-enabling auto-time. But ultimately, likely non of these will help with the issue, as we’ve already mentioned that it is a server problem. Thus, Valve is the one that needs to fix things. We will update the article as soon as we have more information.