...
The Download Basemaps tool uses Esri’s base map services and specifically the export image endpoint. For some reason, Esri decided to set the maxScale parameter within the TPKs it produces. While we have suggest suggested that this is not the expected or desired behavior, that setting persists. This means that if you selected zoom level L15 when downloading the base map, the image completely disappears (won’t display) when you zoom to level 16 or greater. There is a workaround (see below), but it is complex and can’t be completed within MobileMap. Where possible, try to zoom in to as small of an extent as possible, and select a zoom level that meets your needs in the field (e.g., L16). In our experience, downloads greater than 100MB are seldom successful, so you may need to accept a lower zoom level, or break your base map into multiple smaller extent base maps.
...
Check your username in the Authentication Setting and make sure there is not an extra space after your username in the setting. Some tablets and phones automatically add a space after words, including usernames and emails. To fix this open MobileMap Authentication Settings and the ArcGIS Username setting. Backspace over the extra space.
...
...
Upload report show errors on one or more features in MobileMap.
If you get an upload error message, like this message below, while trying to upload your data from MobileMap:
...
If you try adding the data from AGOL using the JSON backup text file you would get this error message:
...
Most likely there is a duplicate field name in the data Here are a couple of things to try:
Check your WiFi connection and try to upload again. CAUTION: This may cause duplicate data if you are creating new features, like trees. Be sure to QC your data after you upload.
Try to add/update the data through Rest Services in AGO using the JSON backup text file. This can help identify if there are data quality issues. You might get an error message like this:
...
Most likely there is a duplicate field name in the data being uploaded causing this error. Duplicate field names can be caused by adding the incorrect field names into some the MobileMap settings. This example below shows two ‘Observer' fields. One with a capital ‘O' and one with a lowercase 'o’:
...
To learn more about data backup and recovery go to https://masonbruce.atlassian.net/wiki/spaces/MD/pages/262212/MobileMap+Data+Backup+Recovery+and+Export#Overview
...
An error occurred. Data may not have been uploaded as expected…
...
One scenario that can create this error is if you accidentally have two feature services selected - the one you are using to collect data and one that is NOT actually being used. While it is possible to utilize two (or more) feature services at the same time, they must all be initialized at the same time. When you select more than one feature service in the ‘Select Feature Services’ you will be presented with a warning message. If you ignore this warning but do not initialize the database, you may experience the error message above.
To resolve this error, open the Actions Menu (third tool button) and choose ‘Select Feature Service’. Inspect the list looking for multiple checked boxes. If you find that one or more feature services was selected in error, uncheck that checkbox and try to upload again.
Another scenario is there is a bad piece of data, or data without geometry, collected. This is more common when collecting point data and not as common when cruising where you are not creating points as you go. One option here is to close MobileMap and reopen from app icon. Then upload again. CAUTION: This may create duplicate data. QC your data carefully.
If this does not resolved the upload error please contact your MobileMap support or submit a ticket via support@woodlandsg.atlassian.net.
...