I'm getting error (Esri.ArcGISRuntime.ArcGISRuntimeException: SQLite constraint violation: SQLite: 19 Abort due to constraint violation)

[RyanDillingham]

I'm getting this error (Esri.ArcGISRuntime.ArcGISRuntimeException: SQLite constraint violation: SQLite: 19
Abort due to constraint violation) using an offline map; and this error "Unable to Submit 1 or more attributes failed" using the same map online. I'm using a Trimble R2 GNSS and Esri Field Maps to collect. 

Here was my general workflow:

• I have been adding GPS metadata to my Esri fields so I can collect x,y,z in the field and get accuracy, etc. 
• I have been using Geoid 18 in Trimble Mobile Manager
• I was collecting points this Monday with Geoid 18, everything worked well
• We received a survey in Geoid 12B that we wanted to overlay our survey onto
• So, in Trimble Mobile Manager, I changed the geoid, but it needed me to download Geoid 12B. I did that Monday night.
• Using the same map and data collection feature, I tried the new Geoid 12B on Tuesday morning. 
• Using the map offline, I got this error "Unable to submit  com.esri.arcgisruntime.ArcGISRuntimeeException: SQLite constraint violation: SQLite: 19   Abort due to constraint violation." 
• Using the map online, I get this error " Unable to Submit 1 or more attributes failed."

I get the same errors when I switch back to Geoid 18. I can use my phone's GPS to collect points and autofill GPS metadata fields, but as soon as I switch to using Trimble R2, I get the errors again. I believe I can collect points using R2 and a point feature that does not have GPS metadata fields. I need to test further. 

Any suggestions? 

[DanielFox1]

Hi @RyanDillingham 

If you are not on the newest version of the app I would try and update the app. In relation to the unable submit error you get please see this community post 

Unable to submit error - 1 or more attributes failed.

This mentions collector but the solution should hopefully work for you also. 

Have you had any schema changes before trying to submit changes?

[RyanDillingham]

Thanks for the suggestion, @DanielFox1.

I did ensure I am using the latest app version. It is up-to-date. Always a good reminder. 

I also reviewed the link you sent. I didn't write any script, so I don't think that is the problem. But similar to @EvoAndreatti and @JosephGrossman , I am using an R2. I have also enabled GNSS metadata attributes. But, unlike @JosephGrossman , I do not think it is the name of the receiver that is the problem because I have been using the same receiver with GNSS attributes enabled for a while now. For me, the problem started when I changed the geoid settings in Trimble Mobile Manager. 

Any other suggestions?

Thanks,  

[RyanDillingham · Accepted solution]

Problem Solved! It was indeed the name of the receiver that was causing the original errors. I made a new feature and added GNSS metadata as I usually do. Then I deleted the column for the receiver name, shared to web layer, added to my map, and was able to collect data again. Weird! So then I shortened the name of the receiver in the R2 settings to 2 letters and it worked. The default name was something like 20 asterisks (i.e. "******************************************"). I still don't understand why I was able to collect data including the name of the receiver before changing the Geoid. But for now I am back in business. 

Thanks for the tips. I hope this helps others moving forward.