Latest Contributions by PreetiMaske

Here is the detailed blog post that explain usage of new auth APIs and how to best use them https://www.esri.com/arcgis-blog/products/sdk-net/developers/new-auth-apis-for-dotnet-sdk Please give this a read, especially `Configuring OAuth` section that particularly talks about OAuth. For OAuth app authentication, pass client ID and client secret directly to OAuthApplicationCredential.CreateAsync. Hope this helps, Thanks ... View more

Hi, Can you please retest this with latest version (200.8) of Maps SDK for .NET. We tested this recently and were unable to reproduce the problem. ... View more

Thanks for the code, I guess you might be running into following issue, which we have identified as bug and plan to fix in Nov release. https://community.esri.com/t5/net-maps-sdk-questions/issue-with-identifygraphicsoverlayasync-and/m-p/1622617 The workaround is to not pass maximumresults parameter value. Please try removing that and let me know if this fixes the issue for you.   ... View more

Yes, we have a great sample on popup viewer our .NET toolkit repo that does exactly what you want https://github.com/Esri/arcgis-maps-sdk-dotnet-toolkit/blob/main/src/Samples/Toolkit.SampleApp.WPF/Samples/PopupViewer/PopupViewerSample.xaml.cs#L29-L121 Just add another case for AggergateGeoElement after https://github.com/Esri/arcgis-maps-sdk-dotnet-toolkit/blob/main/src/Samples/Toolkit.SampleApp.WPF/Samples/PopupViewer/PopupViewerSample.xaml.cs#L62 ``` if (popup.GeoElement is AggregateGeoElement aggregateGeoElement) { return new Popup(aggregateGeoElement, popup.PopupDefinition); } ```   and that should do it. With code if you click on an indiviual feature or a cluster, popup will be displayed accordingly. Hope this helps.   ... View more

If you have both aggregated geoelement and geoelements on the map you will have to tweak your identify code to account for displaying popup in both cases. Properties defined for AggregationFeatureReduction are independent of properties of FeatureLayer. ... View more

@LucaCastenetto , Thanks for reporting the issue. I am able to repro the problem. We will try to get this resolved in one of the near future releases. In the meantime, this can be workaround by not passing the maximumResults parameter to IdentifyGraphicsOverlay method.   Thanks again, Preeti ... View more

Hi Tim,  Thanks for the reproducer, we were able to reproduce this. We have logged an issue internally and assigned to the team responsible for this area. We appreciate your feedback. We will continue to investigate this and try to resolve it. In the meantime, I do have a workaround that you can use, not the best one but will at least unblock youfor now. The workaround below finds the first selected feature and reselects the feature by looking for a matching attribute name `id`. Note my code only selects the first selected feature. You can alter the code to reselect all features as needed. This is just to show the how you we workaround the issue for now. See the updated code below: var currentExtent = MyMapView.VisibleArea.Extent; // Create a query based on the current visible extent. var visibleExtentQuery = new QueryParameters(); visibleExtentQuery.Geometry = currentExtent; visibleExtentQuery.SpatialRelationship = SpatialRelationship.Intersects; // Set a limit of 5000 on the number of returned features per request, // because the default on some services could be as low as 10. visibleExtentQuery.MaxFeatures = 5000; // Get the selected features. var selectedFeatures = await _ogcFeatureLayer.GetSelectedFeaturesAsync(); // Get the id of the first selected feature. var firstSelectedFeature = selectedFeatures.FirstOrDefault(); Int32 id_value = -1; if (firstSelectedFeature != null) { var attributes = firstSelectedFeature.Attributes; id_value = Convert.ToInt32(attributes["id"]); } // Populate the table with the query, leaving existing table entries intact. await _featureTable.PopulateFromServiceAsync(visibleExtentQuery, false, null); // Find the previously selected feature by its ID. var previously_selected_feature = await _featureTable.QueryFeaturesAsync(new QueryParameters() { WhereClause = "id = " + id_value }); // Reselect the previously selected features. _ogcFeatureLayer.SelectFeatures(previously_selected_feature);   If you questions please feel free to reach out. Thanks again, Preeti     ... View more

I haven't tried your code but I have an idea what might be happening. I see you are passing `true` value for `ClearCache` parameter in PopulateServiceAsync, which means all data is cleared from existing table data before loading new results. I don't know what your parameters are for selecting features, but if you are using ID of the feature to query then it will be a different feature everytime because existing data is getting cleared everytime and new results are loaded. ... View more

Sounds like this could be handled by `RemoteCertificateValidationCallback`. Can you give this a try please? https://developers.arcgis.com/net/api-reference/api/net/Esri.ArcGISRuntime/Esri.ArcGISRuntime.Security.AuthenticationManager.RemoteCertificateValidationCallback.html ... View more

Yeah, Video capture helps, I can see the problem but I can't tell if it is publishing issue or Maps SDK issue yet. What API are you using for auto-panning and rotating? What events are you using to trigger pan and rotate as location is changing? Can you share that piece of code? I will see if I can replicate at my end using your code. You can definitely try connecting with support and raise an issue or if you like you can share the MMPK and test app with me and email directly at pmaske@esri.com. ... View more

No, This feature has not yet been prioritized for any near-term release. I will keep you posted if anything changes. ... View more

This is most likely an issue with extent of data in published MMPK. Does it correct itself if you pan or zoom slightly? I am happy to look into more if you can provide the test app and the data. ... View more