Hello again,
I've stumbled across a confusing problem using my watch app with older type or less powerful type watches, and the issue seems to be common on all of them.
First my app pushed over the memory limit for some of them ( 124 ) which caused memory fails.... but at the same time I was getting reports from users with over 1000kB memory of the Position.Info.Track position reporting Null.
In the current form only Fenix 5/6 X / Pro / 945 / D2 can run the app.
First I slimmed down the app which is now around 110kB and peaks around 117 kB.
Then I tried the other Vivoactive and Forerunners. They all load the app, but for some unknown reason with all of them Position.Info.Track appears to be returning null
I've also tried to use Sensor.info.Heading also, and it has the same issue?
No errors during runtime, just returns null?
ideas? It's one of the earliest calculations in my on-compute.
I'm sure that this did not happen previously with them. Is there anything software side that would have changed during an update to cause this issue on older watches?