Project needs update

The Project needs update message indicates that the project item has been updated in your ArcGIS organization. Tap the message to update the copy of the project on this device. Unsent records will remain on the device until they are automatically or manually uploaded, depending on the AutoSend setting chosen in the app.

Any updates made to a layer's schema may result in records failing to upload. If this occurs, you can send the failed records to an email address of your choice.

Records fail to upload

Records may fail to upload for the following reasons:

• Network connectivity may have been lost during the upload.
• One or more project feature layers are unavailable (either deleted or unshared).
• One or more project feature layers had a schema change.
• One or more project feature layers are no longer editable.
• One or more project feature layers had attachments disabled.
• You no longer have permissions to edit content.
• The project is invalid and records can't be submitted from it.
• The submitted value exceeds the size limit of the target field type.

When records fail to upload, a warning symbol is shown on the map button. When you select the map button with a warning, you will see the following options:

• Try again—Allows the user to attempt to submit failed records again.
• Send via email—Creates a database containing all failed records and allows the user to send it via email to the administrator of a project. Sending the database via email does not remove the failed records from the device. If the administrator can resolve the cause of failure, the user can choose Try again.
• Discard—Removes the failed records from the device. Once they are discarded, it is not possible to recover the records. It is recommended to choose Send via email first.
• Cancel—Closes the dialog box.

Data recovery

The Send via email option generates a file with a file name in the format {project name}-{username}-{YYYY-MM-DD-HH-MM}.qrc. This file contains the following:

• A SQLite database that contains three tables: features, layers, and attachments
• An attachments folder containing all captured images
• A collection of .json files describing the geodatabase schema for feature layers

To view the contents of this file, change the file extension to .zip and extract. An example editor for .sqlite databases is DB Browser for SQLite. In the features table of the SQLite database, every record includes the URL of the feature layer to which it belongs. It also includes error messages that should identify the reason submission failed. Common error messages include the following:

• Incorrect geometry type—This may indicate that the layer schema has changed.
• Invalid URL—This may indicate that the layer is no longer available.
• User does not have the privilege to perform this operation—This may indicate that layer permissions have changed.

With this error information, the project author can make changes to allow records to be submitted. After making these changes, the end user should be able to submit the records.

Unable to take a photo

For the mobile app to be able to take a photo, QuickCapture must have system permissions to access the device's camera.

When the mobile app is opened for the first time, you will be prompted to set app permissions. If you decline the permission request, no further prompts or error messages will be displayed, and the mobile app will appear to be stuck waiting to take a photo. Check your device settings to ensure the mobile app has permission to access the device's camera.

Unable to get a location when using the device's internal position source

For the mobile app to get a location when using the device's internal position source, the following must be true:

• The device's Location Service setting is turned on.
• QuickCapture has system permissions to access the device's location.

When the mobile app is opened for the first time, you will be prompted to set app permissions. If you decline the permission request, no further prompts or error messages will be displayed, and the mobile app will appear to be stuck waiting for a location when a project is active. Check your device settings to ensure the mobile app has permission to access the device's location.

Unable to connect to an external GNSS receiver

The most common issue when attempting to use an external GNSS receiver is its Bluetooth connection to your device. Most receivers only allow connection to one device. Confirm that you are not trying to connect to a receiver that has already established a connection to another device. Ensure that Bluetooth is enabled and that the device reports that it has successfully connected to the receiver before you search for it in QuickCapture.

For more information, see Connect your receiver to your device.

Can't capture data

You are unable to capture data while the mobile app is either waiting for the camera to load or waiting for a valid location. Once the camera and location are available, the buttons become active.