Created workshop item returns the wrong ID about steamworks-rs HOT 8 CLOSED

If updating the bindings fixes it, I see no reason to question the change. We should be regularly keeping the bindings and SDK binaries up to date.

from steamworks-rs.

Okay, so Steam creates it with the correct ID, at least according to the log at Steam/logs/workshop_log.txt, leaving me to believe there's either something wrong with the bindings themselves or it's a communication issue between the Steam API and my application.

from steamworks-rs.

After updating the steamworks-sys libs and rebuilding the bindings, it returned the correct ID. I will rebuild the bindings again but with the old libs and see if that already helps.

from steamworks-rs.

Yup, rebuilding the bindings did the trick. Seems like there was some mismatch between the API and the bindings. As I don't know if I can just commit the new bindings.rs or not, I suggest that you should update the bindings and publish a 0.9.1 version.

from steamworks-rs.

The current bindings.rs runs the last steamworks sdk version 153a since #79
I'm a little bit confused about what you did to fix. Can you explain better? Feel free to open a PR too.

from steamworks-rs.

To fix, I literally just cloned the repo, cded into steamworks_sys and ran cargo build --features rebuild-bindings. That already made the file have diffs to the one on the repo. Only thing that might have played into it is that I downloaded the most recent SDK and put the header files into the lib/steam/public dir, so maybe it built the bindings with a different set of headers?

from steamworks-rs.

That is weird. But anyway, if it fixed the problem, you can open a PR :)
@james7132 any thoughts on that?

from steamworks-rs.

So this bug is likely a result of not using platform-specific bindings, meaning it should resolved with #106 .

from steamworks-rs.