I just tried it with my own app, compiled with sdk 2.4.5 for my fenix 5. Simply copied the .prg file onto my new fenix 5 plus and it just worked. Even without adding any fenix5plus product id or anything.
Could someone point me to differences between the 2.4.5 and the current 3.0.11 sdk. Sadly my widget compiles and runs fine with the old sdk, but using the new sdk it compiles without errors, but the simulator returns
"Failed invoking <symbol>
Invalid Value".
Maybe I should start a new thread for that.
Thanks for any help. :)
Best,
Christian
Why would you think there should be? It's moving forward and developers should move forward with it. Backward compatibility would require bloatware on the watch to emulate the old API and HW. If an app IS backwards compatible which it might well be if the API supports it then all good but if not... work to do. Backwards compatibility should not be a requirement in any advance. The option is always there to stay with the old HW.