Latest Contributions by Nicholas-Furness

Great stuff. Good to hear. Would you mind marking some answers as Helpful etc.? Nothing like that Esri Community Karma   Thanks! Nick. ... View more

I'm betting that code is within a func. That func is being exited before the async call returns, and so "table" is being deallocated before the service responds and the block isn't being called. Try making the "table" variable a class variable instead. So something like this. class ViewController: NSViewController {     ...     // Declare "table" here as a class-level variable     // table will not be deallocated just because queryTable() finished.     var table:AGSServiceFeatureTable!         func queryTable() {         // Here we set the class level variable rather than declaring         // a local variable that is deallocated when the function exits.         table = AGSServiceFeatureTable(item: portalItem, layerID: 0)                 let params = AGSQueryParameters()         params.whereClause = "1=1"                 // Fire off the query asynchronously... But...         table.queryFeatures(with: params, completion: { (results, error) in             guard error == nil else {                 print("Error querying... \(error!.localizedDescription)")                 return             }             print("Got a result")         })         // ...the code will exit this function before the query returns.     }     ... }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Note that this isn't going to happen if you're reading from, say, a layer on a map in a mapview with something like (pseudocode alert) mapview.map.operationalLayers[0].featureTable because the map and layer will still be "alive" so you'll be querying against a table that isn't going to be deallocated (it's referenced by the layer which is referenced by the map which is referenced by the mapview which is referenced by the app's UI). In this case what you're seeing is because you're declaring a standalone table item that Swift will deallocate just like any other variable declared in that block. ... View more

Aha. Ok, so that property refers to what's cached locally in the feature table. You would need to set the table's featureRequestMode to Manual for that and call populateFromServiceWithParameters. But that's more advanced than you need… Instead, just call one of the query functions. If you need to know the total record count in the service, use a queryParameter with whereClause of 1=1 and call queryFeatureCountWithParameters to get the result. That's an async operation by necessity. Here are some links that could help: Layers and tables—ArcGIS Runtime SDK for iOS | ArcGIS for Developers  Loadable pattern for asynchronous resources—ArcGIS Runtime SDK for iOS | ArcGIS for Developers  Feature layer query—ArcGIS Runtime SDK for iOS | ArcGIS for Developers  iOS DevLabs: Browse ArcGIS DevLabs | ArcGIS for Developers  Service feature table (no cache)—ArcGIS Runtime SDK for iOS | ArcGIS for Developers  Feature layer (feature service)—ArcGIS Runtime SDK for iOS | ArcGIS for Developers  Service feature table (manual cache)—ArcGIS Runtime SDK for iOS | ArcGIS for Developers  Features and graphics—ArcGIS Runtime SDK for iOS | ArcGIS for Developers  If eventually you need to work with all data locally on the device, those workflows are also supported by the Runtime, but to get started the workflows involve connecting to your hosted service and working against that. ... View more

Hi Trevor. That's Xcode being a pain. I'm sure if you just type the constructor like this it'll compile: let table = AGSServiceFeatureTable(item: portalItem, layerID: 0)‍ let layer = AGSFeatureLayer(featureTable: table) ‍‍‍‍‍‍‍‍ One thought - can you scroll up in that autocomplete list? Perhaps Xcode is scrolling you to the second suggestion for some reason (I think I've seen that before). Alternatively, if you have other errors in the code, Xcode can get confused with what it offers for autocomplete. Xcode gets better at this with each release, in case you're not on the latest. Nick. ... View more

Indeed. I've pointed the .NET team at your question. I did overhear something about whitelisting using the project manifest/settings but since it's way out of my wheelhouse I'll wait for them to pipe up. That might give you something to look into in the meantime though. ... View more

FYI: In Runtime 100, the iOS SDK moved the trustedHosts property to the AGSAuthenticationManager. But we'll get this moved over for the .NET/Xamarin folks to chip in. ... View more

Take a look at the search parameters here. You should be able to use either the access property or the orgid term to build an AGSPortalQueryParameters using queryParametersWithQuery() to pass to the portal.findItems() call. If you use orgid, you can get it from portal.portalInfo.organizationID. Also, since this could return a lot of items, consider paging through the results. Let me know how that goes! ... View more

Thanks for that. This is an issue that we've fixed in version 100. However, that doesn't really help you with version 10.2.5. Are you considering updating to the current Runtime SDK (version 100.x)? ... View more

Looks like the crash happened in Thread 10. Can you provide the stack for that thread please? ... View more

You might try moving your ~/.cocoapods folder out of the way in case it's confused/corrupted by the Cocoapods version update, and doing a fresh "pod install". ... View more

You should use the "rotateEnabled" property of the AGSMapView's "interactionOptions". Seems the Guide documentation is out of date. We'll get it updated. Hope that helps. Nick. ... View more

Have you tried "pod repo update --verbose" to update your local cocoapods repo cache? Failing that, you could try to manually delete the cache folder in ~/Library/Caches/CocoaPods ... View more