Confirmation didn't go through

[cookie]

Just realized one of the offers is stuck and the confirmation did not go through, is there a way around this as I'm only using

SteamCommunity.startConfirmationChecker(12000, s);

Would polling solve this issue? is there any other way around it?

[Dr. McKay]

That's a known Steam issue. Some confirmations just aren't shown by Steam.

[cookie]

That's a known Steam issue. Some confirmations just aren't shown by Steam.

 

Can I provide my own device ID?

[Dr. McKay]

Not presently. Are you confirming stuff in node and on a real phone?

[cookie]

Not presently. Are you confirming stuff in node and on a real phone?

 

in node

[Dr. McKay]

Only in node?

[cookie]

Only in node?

 

Hmm, I have multiple bots some doesn't have a phone. I'll do testing on a bot that is purely independent of mobile phones/desktop applications.

 

Perhaps the one I used had mobile auth registered on an android device, not sure.

Edited March 20, 2016 by cookie

[cookie]

Is calling

SteamCommunity.checkConfirmations();

won't solve the issue?

[Dr. McKay]

The best way to make sure that you don't miss (many) confirmations is to use the same device ID for every confirmation request (on the account).

 

If you use my libraries for confirmations, then you'll always use the same device ID. If you use a node app alongside a real phone, then there can be problems.

[cookie]

The best way to make sure that you don't miss (many) confirmations is to use the same device ID for every confirmation request (on the account).

 

If you use my libraries for confirmations, then you'll always use the same device ID. If you use a node app alongside a real phone, then there can be problems.

 

Device ID as machine ID in steam-user ?

[Dr. McKay]

No, there's a device ID parameter in the URL for all confirmation HTTP requests. As I said, if you're using my libraries then they transparently take care of it for you.