Thanks for the additional details.
Since this only occurs in an iOS Release build and not in Debug, it seems more likely to be related to Release build configuration (linking, trimming, AOT, or LLVM optimizations) than the MMPK content itself.
To help narrow down the cause, could you try the following, starting with the simplest checks?
- Test with the latest 200.8.2 release instead of 200.8.1 to determine whether the issue has already been addressed in a newer patch.
- Run a Release build on the simulator and a Debug build on a physical device to determine whether the behavior is tied to the build configuration or device architecture.
- What type of FeatureLayer.DisplayFilterDefinition is being used: manual or scale-based?
- What are the values of FeatureLayer.RenderingMode and FeatureLayer.TilingMode?
- Is FeatureLayer.DefinitionExpression, ServiceFeatureTable.DefinitionExpression, or FeatureLayer.FloorDefinition also set? If so, what values are being applied?
- For scale-based display filters, verify that the current MapView.MapScale falls within at least one authored display filter range.
- Compare the layer state between Debug and Release builds and check whether the active display filter changes or becomes null after loading.
- Inspect the MMPK JSON (.mmap) and confirm the layer's displayFilterInfo is present and contains the expected values for filterMode, filters, id, where, and activeFilterId.
It would also be helpful to subscribe to GeoView.LayerViewStateChanged and capture the LayerViewStateChangedEventArgs for the affected layer. Specifically:
- Does LayerViewState.Error contain an exception? Is Layer.LoadError populated?
- Does LayerViewState.Status include any of: LayerViewStatus.Error, LayerViewStatus.Warning, LayerViewStatus.OutOfScale, LayerViewStatus.NotVisible
If the issue still reproduces, please try the following Release-build configuration changes:
- Test with linking/trimming reduced or disabled.
- Test with LLVM disabled (and optionally enable the interpreter).
If any of these checks or configuration changes affect the behavior, that would provide a useful workaround and help narrow down the root cause.
Thanks.
