3.0.3 release candidate builds
For those who want to test/upgrade to 3.0.3:
Builds without simulator slice:
Please find attached the change logs for 3.0.3:
The release notes:
[Android and iOS] Added a new API for rerouting from the last matched position. Use this when the route is calculated using a GPX file and a rerouting is needed for navigating on the GPX route from current position.
[Android] Added method setAttributionsLayout. The method can be used to move the Scout and OSM attributions in the four corners of the screen by using the SKAttributionPosition attribute with the values BOTTOM_RIGHT|BOTTOM_LEFT| TOP_LEFT| TOP_RIGHT.
[Android] Added methods for checking the SDK versioning, the name of the SDK version file name, and the traffic status.
BUG FIXES & MINOR IMPROVEMENTS
[iOS] Smaller SDK size (for builds without Bitcode support)
[iOS] Zoom issue fix in the navigation mode
[Android and iOS] Fixed issue with TxgPackageInfoWrapper which caused multiple crashes
[Android and iOS] Fixed reversed lat/long when extended points are requested at route calculation
[Android and iOS] Fixed issue for the didUpdateRouteTraffic delegate method which reported incorrect values for newDurationOfCurrentRoute.
Still a bit confused about the simulator slice or non-simulator slice. In our email conversation you mentioned that the build with simulator slice can't be submitted to the App Store, but I need this build to run and test on the simulator.
Does this mean I have to change the build every time I'm preparing to upload for the App Store? This was not the case with the previous versions of the framework.
Does this build also include a fix for the bug mentioned in this thread: http://forum.skobbler.com/showthread...en-exiting-app (frequent crashes while exiting app)?
The builds with simulator architectures can’t be submitted to the App Store. On 3.0.2 it was the same situation.
Screen Shot 2017-02-17 at 10.20.59.jpg
If you use the non simulator builds, you can run the tests on the apple test devices you are using.
Yes, the builds includes this bug fix.
OK, thanks Adrian. Strange though, I have been using only one build from 2.5.1 onward (also 3.0.2). Tested on simulator with this build and submitting to app store without problems. Could this have something to do with bit code turned on or off? I have it turned off. In any case not a big deal. I have SKMaps set up as a local cocoapods development pod so easy to change. Thanks again for the excellent support. Really appreciate it!
Any chance this includes the android nougat bug fix?
@mrapitis This fix in not included. Our dev team is working as we speak on this. We will release a hotfix when completed.
found 2 issues in iOS objc version:
1. on rotation callout view changes it's coordinates and doesn't point to annotation
2. [[SKReverseGeocoderService sharedInstance] reverseGeocodeLocation:] returns incorrect country name for following coordinates: GPS lon: 24.210327; GPS lat: 56.942188. Country should be "Latvia" but it returns "Germany".
Screen Shot 2017-03-20 at 20.02.43.jpg