At 100.3 I'm getting a The item to be created already exists in the database exception when calling LoadAsync() on a service feature table for some sublayers in a specific on-premise 10.5.1 cached map service.
Here is the complete exception string and I've attached a screen grab of inspecting the exception in debug mode.
Esri.ArcGISRuntime.ArcGISRuntimeException: The item to be created already exists in the database.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at MapWorks.LayerSelection.SelectableItem.<PrepareForUse>d__31.MoveNext() in C:\Users\csmike\Documents\GitHub\MapWorks\MapWorks\LayerSelection.xaml.cs:line 931
This behavior is an improvement over 100.2.x which cratered at the same location despite being wrapped in a try/catch, but I don't have any idea why this is happening or what I can do to mitigate.
Thanks in advance for any suggestions.