Latest Contributions by Nicholas-Furness

‎04-15-2022

Hi @neddyseagoon, It's hard to tell for sure without seeing your data but it's possible that you're doing everything right and the data is just configured not to be visible outside of specific scale ranges? Are you able to share the data with us? Feel free to DM me if so and we can figure out the best way to get it to us.

‎04-15-2022

Hi. The sample loads our global ocean bathymetry basemap for context and displays the ENC chart on top of it, hence the network connection. That basemap is not necessary and the ArcGIS Runtime can work entirely offline, as you need. You could try changing line 22 in the sample to: mapView.map = AGSMap(spatialReference: .webMercator()) Hope that helps!

‎04-13-2022

iOS 15.4 and 15.4.1 introduced a crash in 3D applications built with the ArcGIS Runtime SDK for iOS and ArcGIS Runtime SDK for .NET (Xamarin.iOS / Xamarin.Forms-iOS) which the team have resolved with the 100.13.2 release for those SDKs. See the release notes for iOS and .NET. If your application meets the following criteria, we recommend you release an updated version of your app built with this new 100.13.2 release: Your app uses the ArcGIS Runtime SDK for iOS or the ArcGIS Runtime SDK for .NET. Your app uses version 100.13 or 100.13.1 of the ArcGIS Runtime SDK in question. Your app uses a 3D scene view (2D map views are not impacted). To learn more, including which devices are impacted, please see this blog post. This issue was logged as BUG-000148092 "Navigating a scene view crashes or freezes on newer iOS devices running iOS 15.4.".

‎04-11-2022

Have you tried DisplayFilters? The Definition Expression determines what's obtained from the data source, so if you change that it will make a new request (hence the delay). Display Filters just work with the data in hand. Sounds like you want to use a ManualDisplayFilterDefinition.

‎04-04-2022

Hi. The Runtime SDKs were built from the outset with performance in mind and should be able to handle 10s of thousands of pins with ease. I don't know how you're approaching this to hit that memory spike, but one approach which should certainly work is to set up an AGSGraphicsOverlay on your AGSMapView (add it to the graphicsOverlays collection), and add 1000 AGSGraphics to the AGSGraphicsOverlay's graphics collection. Each AGSGraphic can have its own symbol, but the most efficient way to handle this is to set up a renderer on the AGSGraphicsOverlay, which can efficiently share symbols between graphics in the overlay. If all your points will be displayed the same way, an AGSSimpleRenderer is suitable. Otherwise, if points should be displayed based off an attribute, use an AGSUniqueValueRenderer and populate the attributes dictionary on each AGSGraphic. These samples may help: https://developers.arcgis.com/ios/swift/sample-code/add-graphics-with-renderer/ https://developers.arcgis.com/ios/swift/sample-code/unique-value-renderer/ https://developers.arcgis.com/ios/swift/sample-code/simple-renderer/ https://developers.arcgis.com/ios/swift/sample-code/picture-marker-symbols/ One other thought: if you are using images for your symbols with an AGSPictureMarkerSymbol, be sure the image is a sensible size. You don't need a 10MB image just to display a point on a map. Consider scaling it appropriately. Hope that helps.

‎03-31-2022

FYI: Here is a blog post about this crash. I will accept it as the solution so it appears up front to anyone reading this post.

‎03-31-2022

We have identified an issue displaying a scene view with the ArcGIS Runtime SDK for iOS and the ArcGIS Runtime SDK for .NET (Xamarin.iOS) on iOS 15.4 and 15.4.1. The issue affects iOS and iPadOS devices with an A14, A15, or M1 processor. [ Update, Apr 13 2022: 100.13.2 released, addressing the fix for iOS and .NET (Xamarin.iOS / Xamarin.Forms-iOS) - see blog ] [ Update, Apr 12, 2022: We are preparing an update to fix this issue, targeting release on April 13, 2022. ] [ Update, Apr 5, 2022: We have identified and are assessing a candidate fix. ] When displaying or interacting with a scene view, the scene view may become unresponsive, or the application may crash. 2D workflows (map view) are not affected. The ArcGIS Runtime SDK for Qt is not affected. Only ArcGIS Runtime SDKs version 100.13 and 100.13.1 are affected. ArcGIS Runtime SDKs version 100.12 and earlier are not affected. This issue impacts all applications that display a scene view. No workaround has been identified. We are working to identify the root cause and deliver a fix as a top priority, but at present no ETA is available. [April 5 2022] We have identified and are assessing a candidate fix. The devices that are impacted are: iPhone 12, 12 Pro, 12 Pro Max, 12 Mini (2020, A14 Bionic) iPhone 13, 13 Pro, 13 Pro Max, 13 Mini (2021, A15 Bionic) iPhone SE 3rd Gen (2022, A15 Bionic) iPad Air 4th Generation (2020, A14 Bionic) iPad Air 5th Generation (2022, M1) iPad Pro 11" 3rd Generation (2021, M1) iPad Pro 12.9" 5th Generation (2021, M1) iPad Mini 6th Generation (2021, A15 Bionic) The device must be running: iOS 15.4 iOS 15.4.1 Earlier versions of iOS (15.3.1 and earlier) are not affected. A sample stack trace is provided from iOS to help you identify if you are encountering this crash: Thread 0 [Crashed]: 0 AGXMetalG14 0x1f17f1d50 0x1f1411000 1 AGXMetalG14 0x1f17f6028 0x1f1411000 2 Runtimecore 0x10a72824c esri::rendering_engine::GPU_device_metal::submit_command_(objc_object*, esri::rendering_engine::Command const&, esri::rendering_engine::Pipeline const*) + 1775 3 Runtimecore 0x10a7289e0 esri::rendering_engine::GPU_device_metal::submit_commands(esri::common::Span<esri::rendering_engine::Command, -1l>) + 67 4 Runtimecore 0x10a736b60 esri::rendering_engine::Device::submit(esri::rendering_engine::Render_pass&, esri::common::Span<esri::rendering_engine::Command_set, -1l>) + 83 5 Runtimecore 0x10a084914 esri::map_renderer_3d::View3D::draw(std::__1::shared_ptr<esri::rendering_engine::Device> const&) + 5023 6 Runtimecore 0x109938110 esri::geoview::Scene_view::draw(esri::geoview::Device&) + 143 7 Runtimecore 0x10967fb18 RT_GeoView_draw + 51 8 ArcGIS 0x1059d0280 -[AGSMetalGeoViewRenderer drawRequested] (AGSMetalGeoViewRenderer.m:102) 9 ArcGIS 0x105a084a0 _28-[AGSGeoView setRtcGeoView:]_block_invoke_2 (AGSGeoView.m:260) 10 ArcGIS 0x105a45198 drawRequestedHandler (RTCGeoView.m:298) 11 Runtimecore 0x10995aa28 $std::__1::function<void (void*)>::operator()(void*) const + 35 12 Runtimecore 0x10a868abc esri::common::signal_detail::Signal_base::notify_(esri::common::Function_ref<void (esri::common::signal_detail::erased_target_base&)> const&) const + 351 13 Runtimecore 0x1098ff140 esri::common::Signal<void (esri::geoview::Geo_view const&)>::notify(esri::geoview::Geo_view const&) const + 39 14 Runtimecore 0x109905a8c esri::geoview::Geo_view_draw_requested::draw_request_callback() + 43 15 Runtimecore 0x10a077cb4 esri::map_renderer_3d::Map3D::pulse() + 447 16 Runtimecore 0x109938024 esri::geoview::Scene_view::pulse() + 51 17 Runtimecore 0x109680be0 RT_GeoView_pulse + 27 18 ArcGIS 0x1059d01a4 -[AGSMetalGeoViewRenderer drawInMTKView:] (AGSMetalGeoViewRenderer.m:87) 19 MetalKit 0x1bd7096fc -[MTKView draw] + 183 20 MetalKit 0x1bd717fb8 -[MTKViewDisplayLinkTarget draw] + 39 21 QuartzCore 0x184bb31a0 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 747 22 QuartzCore 0x184d0e0c4 CA::Display::DisplayLink::dispatch_deferred_display_links() + 347 23 UIKitCore 0x184140254 _setupUpdateSequence_block_invoke + 215 24 UIKitCore 0x183aba084 _UIUpdateSequenceRun + 83 25 UIKitCore 0x18413fcb0 $schedulerStepScheduledMainSection + 143 26 UIKitCore 0x18413f478 runloopSourceCallback + 91 27 CoreFoundation 0x180f2cf04 _CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 27 28 CoreFoundation 0x180f3dc90 _CFRunLoopDoSource0 + 207 29 CoreFoundation 0x180e77184 _CFRunLoopDoSources0 + 267 30 CoreFoundation 0x180e7cb4c _CFRunLoopRun + 827 31 CoreFoundation 0x180e906b8 CFRunLoopRunSpecific + 599 32 GraphicsServices 0x19cf2a374 GSEventRunModal + 163 33 UIKitCore 0x1837f5e88 -[UIApplication _run] + 1099 34 UIKitCore 0x1835775ec UIApplicationMain + 363

‎03-30-2022

Thanks for sharing your VTPKs. When I display them in an iPad Pro (with Runtime 100.11 and Runtime 100.13.1), then they appear good: It also looks the same in Pro and a Windows Runtime test app: Also note the size of the red point symbols in my iPad test vs your screenshot, which makes me wonder: What is the DPI of the deployment device? That could help us repro what you're seeing. But… considering the use case, a more fundamental point is that Vector Tiles are static and labels are positioned when the tiles are cooked. Set aside for the moment that they look wrong on the deployment device and pretty good in our tests, I wonder whether longer term for this use case it might be more appropriate to use the Runtime labeling engine with a feature class of street polylines (perhaps in a mobile geodatabase) and suitable label definitions. You could still rely on the VTPK to render the streets themselves, but use transparent line features to place street labels dynamically.

‎03-30-2022

Runtime can certainly honor defined popups and is supposed to, so at this point we would need to see the web map. You say that you saw this behavior on many web maps, so is there one you can share? Otherwise, you could use https://assistant.esri-ps.com/signin to get to the JSON data of the web map and DM me that to take a look. Thank you!

‎03-29-2022

I'm sure that's a typo and you mean iOS 15.4 🙂 We are actively investigating this. At the moment there is no work-around other than to use an earlier version of iOS. I'll reply here when we know more.

‎03-28-2022

Thanks. That's helpful, and strange that you don't see the DM option. Sorry about that. Are you using ArcGIS Runtime 100.13 or 100.13.1? If 100.13.1, did you also see this with 100.13?

‎03-28-2022

I don't find the PM page so I can send you the crash logs. Click on my avatar, go to my profile, and click the Direct Message button.

‎03-28-2022

Thanks for the repro. I don't see the app crash, but I do see the scene view become unresponsive. Will investigate further. If you are seeing crashes, please do share a full stack as it will help us understand more.

‎03-28-2022

Thanks for the additional info. From your screenshot of the portal map viewer, I wonder if the layer has a popup defined, and this is just a question of default behavior when a popup is NOT defined. The title "Spree" probably comes from the service's displayField property. Can you check and see if there is actually an explicitly defined popup in the web map?

‎03-28-2022

Can you please expand and share the entire call stack? Even better, all the threads and the crash metadata. If you're seeing this through the Xcode crash organizer, you can right click on the crash and show in finder. Then please share the .crashpoint file. You can DM it to me.

My Ideas

Latest Contributions by Nicholas-Furness

Re: can not create ENC chart

Re: can not create ENC chart

ArcGIS Runtime SDK 100.13.2 (iOS and .NET) now available

Re: DefinitionExpression Features Hide/Show speed

Re: Map not able to plot large number of pins

Re: Frequent crashes on ios 15.4

Resolved: Crashes in 3D with iOS 15.4 and the ArcGIS Runtime SDK for iOS and .NET (Xamarin.iOS / Xamarin.Forms-iOS)

Re: Runtime labels for streets from vector tile package too few, not matching same data in Pro

Re: AGSField alias / AGSPopupField visible: differences between Runtime and Map Viewer

Re: Frequent crashes on ios 15.4

Re: Frequent crashes on ios 15.4

Re: Frequent crashes on ios 15.4

Re: Frequent crashes on ios 15.4

Re: AGSField alias / AGSPopupField visible: differences between Runtime and Map Viewer

Re: Frequent crashes on ios 15.4

200.8.2 LTS patch for ArcGIS Maps SDKs for Native ...

Re: Spatial Share Testers on Vision Pro

Introducing ArcGIS Maps SDKs for Native Apps 300.0

200.8.1 LTS patch for ArcGIS Maps SDKs for Native ...

Re: Distribution with Lite license