Latest Contributions by MarkDostal

‎02-09-2021

Ok, great. Let us know if you run into any more issues or have additional questions! Mark

‎02-05-2021

Thank you for the further explanation and the code. The error is `Invalid geometry type`. My guess is that you are mixing point, line, and polygons symbols in your composite symbol. They all need to be the same geometry type when added to the composite symbol. Please double-check the symbol types (point/line/fill) that get added to the composite symbol. Let me know how that goes, Mark

‎02-02-2021

The San Diego Places is one layer; the data in the layer is symbolized using "Unique Values". The LegendInfos represent those unique values and are what is drawn in the image I posted. The web map used in the Legend example is here. You can take a look at the various layers, how they are symbolized and how they appear in the map's legend in the online map viewer. The LegendInfo mechanism was designed to be displayed with the symbol/name given, so creating a composite symbol is not really standard. The swatch should be created from the symbol property of the LegendInfo. You can see that in the LegendViewController here. If you're still seeing the error, you can send it to me along with an explanation/code snippet of what you're doing and I can take a look. Mark

‎02-02-2021

Thank you for your question! It is possible to use the symbols in the legendInfos to create a composite symbol. What would be the use case for doing that? A legendInfo represents one individual legend element, so combining their symbols may be confusing. Example: each of the rows (Food, Fun, Design) in the image below is represented by a single legendInfo. As for `AGSArcGISMapImageLayer`, each of it's sublayers is also "Loadable", which means you need to load them explicitly in order to have their properties populated. If you look in `LegendViewController.swift`, in the method loadIndividualLayer, it loads the layer, then calls loadSublayersOrLegendInfos, which loads the sublayers. Only after the sublayers are loaded does it call fetchLegendInfos and get the legendInfos it uses to build the legend. So I suspect if you explicitly load the sublayers before calling fetchLegendInfos, you should be OK. Please let us know if you need more information or have more questions. Mark

‎01-28-2021

This release includes: - Addressed a couple linting issues that showed up after upgrading to SwiftLint 0.41.0. - Updated paths for ArcGIS.xcframework as the ArcGIS Runtime SDK for iOS, v100.10.0, now builds as a dynamic framework and is installed in a new location. - Modified Example app project file to embed Swift standard libraries only when necessary. - Fixed a crash in the TemplatePickerViewController when reloading rows. - Updated examples to use the new `AGSMap` constructors that take a basemap style. - Documented API key functionality (needed for new basemap styles) in Example app’s `AppDelegate.swift` file. - Made sure to forward the appropriate app delegate method regarding download tasks to ArcGIS. - Documented, in the PopupController’s README, required Info.plist entries for adding image attachments. - The “Yosemite - Tabletop” and “US - Mexico Border - Tabletop” options in the AR Example have been removed as the data backing them is no longer available. You can find the Toolkit here. See this blog post for information on the SDK release. We hope you enjoy the new release! Let us know what you're building with it.

‎01-25-2021

Thank you, I will pass that on!

‎01-25-2021

I have created an internal issue for this problem and have forwarded it on to the appropriate team. I was able to reproduce the issue both in the Simulator and on a device, although it took me a minute or two of panning/zooming around Honolulu to get it to crash. As of this time, I don't have a work-around for you, except to try a different base map. Mark

‎01-22-2021

Thanks for the additional info. I was able to reproduce the crash locally with the map you sent in the simulator, but I got a different call stack. I'll keep you posted on what I find out. -Mark

‎01-22-2021

I'm sorry to hear you are having problems. The crash dump is great and helps a lot. Can you provide some additional info which will help us debug this? - Runtime SDK version (100.9, 100.8, etc.) - Xcode version - Does the crash happen on simulator or device or both? - iOS version the crash happens on? - If on device, which model iPhone/iPad? Thank you. Mark

‎08-27-2020

The latest release of the ArcGIS Runtime Toolkit for iOS is here. It has been updated to work with the 100.9 release of the ArcGIS Runtime SDK for iOS. This release includes: Fix for an issue when creating a BookmarksViewController using the public init<S: Sequence>(bookmarks: S) where S.Element == AGSBookmark constructor. The array was not properly updating the underlying table view and therefore no bookmarks would appear in the table. You can find the Toolkit here. See this blog post for information on the SDK release. We hope you enjoy the new release! Let us know what you're building with it.

‎07-15-2020

Kenneth, Take a look at the code Nick posted, it show's how he's creating the custom view. Specifically: class MyCustomView: UIView { static let instance = Bundle.main.loadNibNamed("CustomCalloutView", owner: nil, options: nil)?.first as? MyCustomView and: mapView.callout.customView = MyCustomView.instance I think with both Nick and I helping out we'll get you sorted. 😉 Mark

‎07-15-2020

I tried it here and got it to work. The `AGSCallout` uses constraints to set up the custom view. What I did was use constraints in the .xib, along with setting the "layout" to `Automatic` (as opposed to translating mask to constraints). See the screenshots below. Let me know if that doesn't work for you and I can dig further. Mark this was both for the view and the label: The code from `didTapAtScreenPoint`: let projectedPoint = AGSGeometryEngine.projectGeometry(mapPoint, to: .wgs84()) as! AGSPoint customCallout.message = "Coordinates\n Original: \(mapPoint.x), \(mapPoint.y)\n Projected: \(projectedPoint.x), \(projectedPoint.y)"

‎07-14-2020

I would suggest removing the call to set the self.frame property in the MapCalloutMessageView.init method. The documentation for the AGSCallout.customView property states: The callout will expand to fit the dimensions of the custom view. That should handle the sizing for you. You can also look at the ArcGIS Runtime Samples for iOS repo on GitHub, specifically, the Geometry/Project sample which uses a custom callout similar to what you want. The code for that is here. Let me know if you still have problems. Mark

‎05-11-2020

The latest release of the ArcGIS Runtime Toolkit for iOS is here. It has been updated to work with the 100.8 release of the ArcGIS Runtime SDK for iOS. This release includes: JobManager changes: Use UIApplication.shared.beginBackgroundTask instead of the background fetch stuff. Background fetch can take hours to get called according to the Apple documentation. Instead, beginBackgroundTask keeps the app alive for up to 10 minutes, giving most jobs the ability to finish or at least get to get out of the process download phase. Auto Layout fixes for JobManagerExample and MeasureToolbar. Updates minimum iOS version to 12.0 and Xcode version to 11.0 to keep inline with the ArcGIS Runtime SDK for iOS. Fixes deprecation of UISearchController.dimsBackgroundDuringPresentation resulting from iOS 12.0 update. Change locationDataSource property of ArcGISARView to be of type AGSLocationDataSource instead of the subclass AGSCLLocationDataSource. You can find the Toolkit here. See this blog post for information on the SDK release. We hope you enjoy the new release! Let us know what you're building with it.

‎04-08-2020

Tom, Sorry to hear you're having problems. Take a look at the information here which fixes a similar issue. If that does not fix your issue, please reply with the iOS version, Xcode version (and ideally a stack trace) and any other pertinent info and I can take a look. Mark

Online Status	Offline
Date Last Visited	‎08-18-2025 09:06 AM

My Ideas

Latest Contributions by MarkDostal

Re: LegendInfos

Re: LegendInfos

Re: LegendInfos

Re: LegendInfos

ArcGIS Runtime Toolkit for iOS v100.10 is live!

Re: Esri_runtimecore crashes when using OSM Vector Basemap

Re: Esri_runtimecore crashes when using OSM Vector Basemap

Re: Esri_runtimecore crashes when using OSM Vector Basemap

Re: Esri_runtimecore crashes when using OSM Vector Basemap

ArcGIS Runtime Toolkit for iOS v100.9 is live!

Re: Custom callout not shown properly

Re: Custom callout not shown properly

Re: Custom callout not shown properly

ArcGIS Runtime Toolkit for iOS v100.8 is live!

Re: Simple iOS app does not work on device

Introducing the ArcGIS Maps SDK for Swift Toolkit ...

Introducing the ArcGIS Maps SDK for Swift Toolkit ...

Introducing the ArcGIS Maps SDK for Swift Toolkit ...

Re: Is augmented reality missing from ver. 200?

Re: Differences in Arcgis Runtime SDK for iOS and ...