It is not a bug, but rather cumbersome problem. The issue is that iPhones do not have stable magnetic sensors and so their North is different in every initialisation - ranging from -90 to +90 degrees! So Id love to change the location orientation value to update to this new "North".
I can get the orientation before initialisating the view, but I cant change it in the fetched location (and rebuilding it every time is not really good solution I believe). If we simply could update the orientation vector, this would hugely befit the rotation accuracy the app provides.
I could be fine with rebuilding fetched location with the new parameters but this is impossible as well, because there is no SDK documented way of converting fetched ELILocation into ELIBuilder object.
It is not a bug, but rather cumbersome problem. The issue is that iPhones do not have stable magnetic sensors and so their North is different in every initialisation - ranging from -90 to +90 degrees! So Id love to change the location orientation value to update to this new "North".
I can get the orientation before initialisating the view, but I cant change it in the fetched location (and rebuilding it every time is not really good solution I believe). If we simply could update the orientation vector, this would hugely befit the rotation accuracy the app provides.
I could be fine with rebuilding fetched location with the new parameters but this is impossible as well, because there is no SDK documented way of converting fetched ELILocation into ELIBuilder object.