Problem with confirmations while using different devices

[0x737368]

So currently I write my bot on my regular computer, and once it's tested I upload it to my RaspberryPi so it could continue to run while my computer is off. However, this brings the issue that when there's a trade offer that needs to be confirmed it gives me this error: 

Error: Could not find confirmation for object $offer.id

Is there some sort of "cooldown" period for it to be able to work from the Pi or some way to reset it?

 

I guess it shouldn't be a problem once the bot is finished, but whilst I'm developing it I'd like to be able to run it from both my computer and R.Pi.

 

Thanks

Edited June 7, 2017 by 0x737368

[Dr. McKay]

It shouldn't be a problem as long as you aren't also trying to confirm stuff on a phone.

[0x737368]

I'm not confirming trades on my phone, and yet it still throws that error when I offer it a trade that requires confirmation.

Anyway, I guess I'll leave the bot running on the pi and see if the trade goes through at some point.

[Dr. McKay]

Are you using the same modules to confirm trades on both devices? I'd assume you are, but it can't hurt to make sure. If you're using the same modules, code, and account, then there shouldn't be a problem...

[0x737368]

They're exactly the same. I'll keep the bot running on the Pi overnight to see if it'll reset at some point, but so far each time I tried sending it an offer requiring a confirmation it still gave me the error.

[0x737368]

It's been more than 24 hours and it still gets the confirmation error on the Pi. Any ideas on how to circumvent this? 

I figured it would be a good idea to add that I'm using steamcommunity's acceptConfirmationForObject instead of the traditional confirmationObject.respond, could this be somehow responsible?

Edited June 8, 2017 by 0x737368

[0x737368]

Alright, so I decided to rewrite the accept confirmation function with confirmation.respond, hoping I could get some insight into the problem. 

When starting up the confKeyNeeded event is sent with a "conf" tag, just like on the PC, however on the Pi I never get a "newConfirmation" event. I'm beginning to wonder if this has something to do with the Pi itself, so tomorrow I'll fire up my old laptop if it's still alive and see if it works there. 

[0x737368]

Alright, checked it on my laptop and it works just fine. So for some reason the "newConfirmation" events are not coming through on the Pi.

Could this be an issue with the node port for ARM architectures? Anyway, I guess that's a question for another forum.

[0x737368]

Reinstalled all the modules on the RaspberryPi and it worked!