Latest Contributions by JeremyBridges

‎10-05-2020

Runtime for Xamarin, 100.8

‎10-05-2020

FYI: we received the following stack trace from our telemetry recently. This was using the .NET Runtime running on iOS, using Xamarin. Hopefully, it helps to fix some bugs that haven't been discovered yet. System.ArgumentException: Invalid argument: The position's spatial reference is null Stack trace: at Esri.ArcGISRuntime.ArcGISException.HandleCoreError (RuntimeCoreNet.GeneratedWrappers.CoreError error, System.Boolean throwException) at RuntimeCoreNet.GeneratedWrappers.Interop.CheckError (System.IntPtr errorHandle, System.Boolean throwOnFailure, System.Runtime.InteropServices.GCHandle wrapperHandle) at RuntimeCoreNet.GeneratedWrappers.CoreLocation..ctor (RuntimeCoreNet.GeneratedWrappers.CoreDateTime timestamp, RuntimeCoreNet.GeneratedWrappers.CorePoint pointHandle, System.Double horizontalAccuracy, System.Double verticalAccuracy, System.Double velocity, System.Double course, System.Boolean lastKnown) at Esri.ArcGISRuntime.Location.Location..ctor (System.Nullable timestamp, Esri.ArcGISRuntime.Geometry.MapPoint position, System.Double horizontalAccuracy, System.Double verticalAccuracy, System.Double velocity, System.Double course, System.Boolean isLastKnown) at Esri.ArcGISRuntime.Location.SystemLocationDataSource.RaiseLocationChanged (Esri.ArcGISRuntime.Internal.Geoposition geoposition, System.Boolean isLastKnown) at Esri.ArcGISRuntime.Location.SystemLocationDataSource.Locator_PositionChanged (System.Object sender, Esri.ArcGISRuntime.Internal.PositionChangedEventArgs args) at Esri.ArcGISRuntime.Internal.Geolocator.OnPositionChanged () at Esri.ArcGISRuntime.Internal.Geolocator.UpdateCurrentPosition (CoreLocation.CLLocation location) at Esri.ArcGISRuntime.Internal.Geolocator.LocationManager_LocationsUpdated (System.Object sender, CoreLocation.CLLocationsUpdatedEventArgs e) at CoreLocation.CLLocationManager+_CLLocationManagerDelegate.LocationsUpdated (CoreLocation.CLLocationManager manager, CoreLocation.CLLocation[] locations) at (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr) at UIKit.UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate) at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName)

‎08-12-2020

Got this reply from one of the devs on the Server team: I think in this case the underlying replica is a 2 way replica even though the FS sync limits it to only sync download (based on only query and sync capabilities). As I remember, a 2 way replica is always created behind the scenes as it can support any of the sync direction options the feature service may be configured to support. In this case you could publish the feature service using the databases SDE user but limit the FS capabilities to query and sync. That way non-owners / non-admins will not be allowed to edit the data through the feature service (data is still protected via the FS) but the back end server SOC process will work as it will connect as SDE. Great advice. Thanks you!

‎08-12-2020

A client of ours wants to protect their Default version from edits by non-owners or non-admins, yet still allow them to take sync replicas from a feature service and keep them updated. The remote users will not have edits to transmit back to the enterprise. They just need to get updates that are added to Default. Seems best to enable only Sync and Query on the feature service. What other steps should they take to allow them to use sync replicas in this way?

‎05-14-2020

Currently, the magnifier is a useful tool for viewing elements on the map in a closer way. But, it isn't very useful when a user is manipulating elements of the map. For instance, if you want to allow a user to place a marker with precision, even when using their finger, the magnifier would be the perfect tool to allow them to see the map under their finger and move something to exactly the spot they desire. We can then build custom tools to enhance that experience and know when the magnifier is shown and when it isn't.

‎04-22-2020

Our app is crashing when trying to access the Table property of a ServiceFeatureTable. Part of the call to that gets down to the core CoreArcGISMapImageSublayer.CoreRT_ArcGISMapImageSublayer_getTable method. That method throws an AccessViolationException for some unknown reason. Two issues with this: We have a try-catch around this, the exception still crashes the app. Not sure how that's possible. The exception doesn't tell us why it is thrown. We can't fix without that info. Love to hear from you guys. Thanks in advance!

‎04-01-2020

We've noticed the issue on Xamarin (iOS) and WPF. We'd love to test in both places. For reference, our workflow is very similar to Johnathan's. We store the refresh token on login. It is placed in the Runtime's OAuth authentication API's on start of the app, or after login. We know we've needed to call RefreshTokenAsync in order to get Runtime to work correctly with federated services. Our code: var serverInfo = new ServerInfo { ServerUri = portalUri, TokenAuthenticationType = TokenAuthenticationType.OAuthAuthorizationCode, OAuthClientInfo = new OAuthClientInfo { ClientId = appClientId, RedirectUri = redirectUri } }; AuthenticationManager.Current.RegisterServer(serverInfo); var cred = new OAuthTokenCredential { Token = accessToken, OAuthRefreshToken = refreshToken, ServiceUri = portalUri, GenerateTokenOptions = new GenerateTokenOptions { TokenAuthenticationType = TokenAuthenticationType.OAuthAuthorizationCode } }; AuthenticationManager.Current.AddCredential(cred); await cred.RefreshTokenAsync();

‎04-01-2020

It is not fixed, at least in our use case. We'll start up a ticket. Any bug numbers or other ticket numbers we can put on the ticket so its easier to associate with the original issue?

‎03-31-2020

Were you guys able to address this issue in 100.7? We are seeing the same issue. We're updating from 100.5.

‎03-02-2020

Alright. Could you give us a better picture of why this is the only remedy? Is it dependent to the fundamental nature of the database infrastructure a geodatabase relies on (relational database)? Also, can we get a better error message? "Object is Missing" doesn't communicate enough for an application to manage the transaction in a more automatic fashion. At the very least, we'd love to see the response body contain the layer ID and GlobalID/ObjectID of the problem record. Something like: { "error": { "code": 400, "message": "Update failed on object from 'Transformer' layer, GlobalID 'abc....' - object doesn't exist" "details": [ {"layerID": 0}, {"globalID": "abc..."} ] } }

‎02-24-2020

Our clients mainly use versioned data for everything. From what we've learned about rollbackOnFailure, it cannot be set to false for versioned data. So unfortunately, this approach is viable for us. Is our best practice here to query for possible conflicts before applyEdits, or is there another, more attractive approach?

‎02-20-2020

Updating or deleting a record that does not exist causes the entire ApplyEdits call to fail with 400 "Object is Missing" and no other information. We think we may need to either query for records before calling ApplyEdits in attempt to pre-detect potential conflicts or call ApplyEdits once per feature for updates and deletes in order to determine which features are problematic. What is the recommended approach to better handle these situations?

‎02-20-2020

ArcGIS Server does not use a GlobalID we provide in applyEdits, so we do not have a reasonable way to prevent duplicate inserts. Are we correct in assuming that the caller can only specify GlobalIDs for non-versioned data? Is there another recommended solution?

‎02-14-2020

We have many customers who like to have their users login once and never have to re-login. The secure OAuth workflow that continually generates auth tokens from a never-expiring refresh token is a reasonable security risk to them. Please allow the admin to set a refresh token expiration timeout that is whatever the organization desires, including disabling the timeout. Related documentation: Specify the default token expiration time—Portal for ArcGIS (10.8) | Documentation for ArcGIS Enterprise

‎02-10-2020

That's good to know. We'll likely push folks to the later versions of the app if we get support tickets on the error. So, I don't think any more diagnosis will be necessary. If we get an instance on 100.7, we'll let you know. Thanks for the info!

Online Status	Offline
Date Last Visited	‎08-04-2025 02:26 PM

My Ideas

Latest Contributions by JeremyBridges

Re: Null spatial reference inside location manager

Null spatial reference inside location manager

Re: How to set Default version to Protected and update sync replicas?

How to set Default version to Protected and update sync replicas?

ArcGIS Runtime: Magnifier events (shown, hidden)

Cannot catch AccessViolationException coming from CoreArcGISMapImageSublayer.CoreRT_ArcGISMapImageSublayer_getTable

Re: ArcGISWebException code 498: "invalidated refresh_token"

Re: ArcGISWebException code 498: "invalidated refresh_token"

Re: ArcGISWebException code 498: "invalidated refresh_token"

Re: How do we handle conflicts when using ApplyEdits?

Re: How do we handle conflicts when using ApplyEdits?

How do we handle conflicts when using ApplyEdits?

How do we handle idempotency in Server's applyEdits?

Allow any expiration timeout for Portal refresh tokens, including no timeout

Re: Exception - "device or resource busy" in RT_MapView_locationToScreen

Re: How to obtain feature service layer definition...

Re: How to set Default version to Protected and up...

How to set Default version to Protected and update...

Allow any expiration timeout for Portal refresh to...

Re: Deploying ArcGIS Server using Docker