Attached is a small MMPK, created in Pro 2.0, that demonstrates a bad symbol rotation in Runtime 100.1 [I don't recall seeing this issue in Pro 1.4.1/Runtime 100.0, but I may be wrong].
Here's how it appears imported into Pro:
And here's how it appears in Runtime:
Ah, ofc. I was using an offline map and not mmpk file so you cannot access the geodatabase directly. As a workaround you need to do something like this then.
offlineMapPackage = await MobileMapPackage.OpenAsync(offlineDataFolder);
offlineMap = offlineMapPackage.Maps.First();
await offlineMap.LoadAsync();
var featureLayers = offlineMap.OperationalLayers.OfType<FeatureLayer>().ToList();
var featureLayer = featureLayers.First();
var gdbTable = featureLayer.FeatureTable as GeodatabaseFeatureTable;
var gdb = gdbTable.Geodatabase;
var pointLayers = new List<int>();
for (int i = 0; i < gdb.GeodatabaseFeatureTables.Count; i++)
{
var table = gdb.GeodatabaseFeatureTables[i] as GeodatabaseFeatureTable;
if (table.GeometryType == GeometryType.Point)
pointLayers.Add(i);
}
offlineMapPackage = await MobileMapPackage.OpenAsync(offlineDataFolder);
offlineMap = offlineMapPackage.Maps.First();
featureLayers = offlineMap.OperationalLayers.OfType<FeatureLayer>().ToList();
featureLayer = featureLayers.First();
gdbTable = featureLayer.FeatureTable as GeodatabaseFeatureTable;
foreach (var index in pointLayers)
{
var table = gdbTable.Geodatabase.GeodatabaseFeatureTables[index];
table.UseAdvancedSymbology = false;
}I couldn't figure other ways to workaround with this and the solution includes opening the mmpk twice. You can clean up the approach a bit but at least it works. The code below only work directly with mmpk that only has one geodatabase inside of it so if you have multiple, then you need to add logic to iterate the layers etc. I'm not sure what we can do to make this easier but I'll log an enhancement ticket for it.(EDIT: except fix the original issue so the workaround isn't needed)
