Latest Contributions by dotMorten_esri

Yes a few of the draw operations are a drag, not a click+click like polygon. ... View more

Are you doing the mouse-down+drag operation and don't even see a circle getting drawn? Or just not seeing the events fire? Which platform are you targeting? ... View more

What are the label expressions you use on each graphics overlay? How are you assigning them to the overlays? ... View more

It looks to me the surface isn't loaded in your mobile app. Are you hitting an http or https service? Note that both android and ios by default blocks http services now, so could just be the surface data fails to load. ... View more

Which services are in the map you're taking offline? Are you sure these are vector services, and not raster services? ... View more

> Like I mention, because the value of lat/lon in the database are correct, it seems to me that point itself is valid.  I'm a little confused here. You mentioned the issue was with the time stamp you're writing, not the geometry. Have you (in addition to validating the geometry), validated that the time stamp you're getting from your custom NMEA datasource is actually correct? ... View more

It's not clear to me when you say this problem occurs. Does the problem occur with the location you get from the NMEA Parser, does it occur when you insert, or does it occur after it got into the database? What did you do to validate that the location coming from the NMEA parser is valid before adding it to the table?   I wouldn't read much into what the sqlite database functions interpret that number value as. It's not what we use, and it doesn't appear like the datetime() sqlite function takes a double, but an integer I think. > I should note that when this occurs many of the GNSS fields are null, so that data may not be picked up from the receiver You should probably validate that the location is valid and a proper fix and timestamp before using it? ... View more

>  But in a high number of the offline *.geodatabases that fail to sync when this data is exported to cvs and opened in Excel the ESRIGNSS_FIXDATETIME comes in as a number and does not get converted to a date I'm not sure which process you use here to do that, but note that the local geodatabase format doesn't actually support dates and uses an epoch number instead to store dates. It's the schema of the table that tells us that the number should be interpreted as a date.   > This does not throw an exception, but it writes the invalid value. I'm not sure what you mean by "the invalid value" ? What makes it an invalid value? In your check for whether the timestamp is null or not, can't you also validate what value it contains? Also I'm not entirely sure why you're converting the timestamp to DateTime? Attributes should generally be using DateTimeOffset instead of DateTime. So you can replace nmeaLocation.Timestamp.Value.UtcDateTime with nmeaLocation.Timestamp.Value       ... View more

As Calvin is hinting at, the maximum size you can take offline is limited in the service's settings. If you own the service, you can increase that limit - if you don't own the service, you're at the mercy of the owner and have to stay within the maximum limitation. Note that a cache for the entire world could be several terabytes! ... View more

Try loading the layer explicitly and see if an error is thrown (and what that error is): try { await tileLayer.LoadAsync(); } catch(System.Exception ex) { // Inspect ex here }   I'm guessing the issue is your app might not be able to directly read from the path you're specifying. ... View more

A callstack would definitely be helpful. Otherwise it's just pure guesswork what went wrong. > I have been able the intercept the exception before the app closes and I’m encountering a null reference exception [...] At the moment I am not able to add any stack trace info, but will do this later. If you're able to intercept it, at that breakpoint you should be able to see the stacktrace. Also you can try enabling break on any null reference exception in the exception settings:   ... View more

If you have a chance, could you try and upgrade Visual Studio to the latest 16.8.0+ and see if this resolves your issue? We've seen one other case where this resolved it for them. ... View more