POST
|
The Esri rep left me a message today. It does seems specific to 14.7.1, so downgrading is the only workaround they have at the moment.
... View more
08-25-2021
11:09 AM
|
3
|
0
|
1140
|
POST
|
I asked for an update this morning. I have not heard anything since Thursday.
... View more
08-24-2021
10:14 AM
|
0
|
0
|
1154
|
POST
|
The crash seems to be related to the external location providers. I have notified Esri with a more detailed reproduction; hopefully they can get a fix out soon. Thank you!
... View more
08-19-2021
12:27 PM
|
1
|
2
|
1712
|
POST
|
Is your field worker using an external location provider? Is it a Trimble R2?
... View more
08-19-2021
12:19 PM
|
0
|
4
|
1717
|
POST
|
I was able to take it out for 60 to 90 minutes yesterday without any problems. I probably never changed apps that entire time. Just for fun, I tried to launch the app again and… it crashed. So that was not a permanent solution for me either. I will have to wait until tomorrow to take a look at this or talk to esri.
... View more
08-17-2021
01:22 PM
|
0
|
1
|
1746
|
POST
|
When I tried to open QuickCapture on an iPad Mini (5th gen) version 14.7.1 this morning, it would hit the splash screen then close after a few seconds. There were no logs recorded as far as I could tell. I tried restarting the iPad to no avail. The iPad had been updated last week, and I do not believe I used QuickCapture between the system update and today. It was crashing before and after I applied the August 2021 update. I had made no changes to any QuickCapture projects. To resolve I reinstalled QuickCapture. edit: as AndrewDeLuca pointed out in a comment, this is not a permanent fix. I was able to use it for over an hour without issue, but it started crashing again.
... View more
08-16-2021
06:04 AM
|
1
|
27
|
3578
|
POST
|
To add to this a bit, you typically create a Web Map to be an important component of a Web App. The "App" is all the widgets and extra bits that help narrow the focus of the underlying web map.
... View more
08-13-2021
12:57 PM
|
1
|
0
|
685
|
POST
|
That was causing the issue with mine. You can try running the feature class to feature class script with "Output has M Values" as "Disabled" under the Environments tab (as at the bottom of the attached image) and publishing the result to AGOL.
... View more
10-13-2020
07:17 AM
|
2
|
0
|
3561
|
POST
|
Reid, does your layer have m-values, and are any of those m-values NaN for your features?
... View more
10-13-2020
07:06 AM
|
0
|
2
|
3561
|
POST
|
I opened up a ticket yesterday. I have a call with ESRI support today. I'll keep you posted.
... View more
10-13-2020
05:45 AM
|
0
|
0
|
3561
|
POST
|
Here's some more information I left out. The feature class is in a file geodatabase, and I published it to AGOL in ArcGIS Pro v2.6.2. I have also used the "feature class to feature class" tool to copy the troublesome features to a different file geodatabase with no luck. I also tried copying just the geometry to a new feature class with no luck.
... View more
10-08-2020
12:39 PM
|
0
|
0
|
3561
|
POST
|
EDIT: NaNs for m-values seem to be the culprit. After moving the features to a class with m-values disabled, everything is drawing properly. The feature class that is drawing correctly is the route layer for a (now deprecated) linear referencing system. All the m-values are correct. I moved away from the LRS for our street model because ArcGIS Pro lacks good editing features for LRSs, but I left the m-values. After making edits to the routes, there were vertices with NaN m-values. Those NaN m-values seem to cause this drawing issue. Original post: I have a layer of street centerlines that is not drawing beyond the 200ft scale in an AGOL web map when editing is turned off or in a view layer. It does draw at small scales when editing is enabled. In the Visualization tab for the feature layer, the entire layer is drawn correctly. I have tried the layer as multipart and single part features. I have tried turning on optimized layer drawing (and it has been multiple hours since, so I assume that is complete). As single part there are 531 features with a total of 24,932 vertices, and the largest single line vertex count is 725. A few months back I uploaded a very similar feature layer (the layer's local source was corrected, and that corrected layer is the one causing problems) with nearly identical features. This layer has 391 multipart features with 24,796 total vertices and a single line vertex count max of 1,047. This layer draws at all scales and never had optimized layer drawing enabled. This layer works with editing on or off and has a functional view layer. Have I misconfigured my feature layer somehow? Here is a map with both the view layers: https://arcg.is/1WXWCr Tested in Chrome and Edge.
... View more
10-08-2020
12:29 PM
|
0
|
6
|
3652
|
POST
|
I'm aware of 'with', but the OP did not use 'with'.
... View more
08-03-2020
01:19 PM
|
0
|
1
|
1091
|
Title | Kudos | Posted |
---|---|---|
3 | 08-25-2021 11:09 AM | |
1 | 08-16-2021 06:04 AM | |
1 | 08-19-2021 12:27 PM | |
1 | 08-19-2021 08:15 AM | |
1 | 08-13-2021 12:57 PM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|