Forum Discussion
Version incompatibility 1.4
Hi,
I just released a beta for our VR application. It was built using Oculus SDK for Windows 1.3.
All of a sudden users started complaining about the application failing to start due to:
Version incompatibility: Callee function signature does not match caller.
It seems to happen because the users have:
1. Updated their runtime
2. Updated their firmware
How do we as developers protect ourselves against this?
Can I as a developer get hold on the runtime before it is released to the general public?
Thanks,
/J
I just released a beta for our VR application. It was built using Oculus SDK for Windows 1.3.
All of a sudden users started complaining about the application failing to start due to:
Version incompatibility: Callee function signature does not match caller.
It seems to happen because the users have:
1. Updated their runtime
2. Updated their firmware
How do we as developers protect ourselves against this?
Can I as a developer get hold on the runtime before it is released to the general public?
Thanks,
/J
1 Reply
- I realized that we distributed LibORTRT64_1.dll ourselves instead of letting Oculus and the env path variable take care of it. So the problem has been solved.
Even so, would be great if I as a developer could get an email if there are interface breaking releases in the future.
