Common problems¶
Start here when something fails. Pick the symptom that matches what you see.
My fields don't appear in Transform¶
What you see: Output Fields is empty, or Add transformation has no columns.
Why it usually happens: GeoJibe learns field names from inspect. Upload is still reading, or a URL/S3/FeatureServer Source has not been Imported yet.
What to check: Wait for inspect to finish. For URL, S3, and ArcGIS, click Import (or Connect, then Import). Then open Transform again.
My URL won't import¶
What you see: Import fails, times out, or the URL is rejected.
Why it usually happens: The link is not public http/https, the file is not a spatial dataset, or the host is private/internal.
What to check: Open the URL in a browser without signing in. Use S3 or Upload for private files. FeatureServer URLs should use the ArcGIS Source.
My Python script didn't create an output file¶
What you see: The Python script did not create the output file.
Why it usually happens: The script ran but never wrote sys.argv[2].
What to check: Print or write to sys.argv[2]. A df.rename(...) example does nothing unless you also load data and save that path. See Python scripts.
GeoServer rejected the publication¶
What you see: Store or layer already exists, workspace missing, or not vector.
Why it usually happens: GeoJibe only creates a new store and layer. The workspace must already exist. Data must be vector with geometry and a CRS.
What to check: Pick a new store/layer name. Create the workspace in GeoServer first. Publish one layer from a multi-layer file.
GeoNode upload failed¶
What you see: Resource name exists, unsupported GeoNode, or processing never finishes.
Why it usually happens: Names must be unique. Very old GeoNode has no upload API. Processing on GeoNode can take several minutes.
What to check: Test the Destination. Use a new resource name. Confirm the site is GeoNode 5 or 4.2+.
QFieldCloud projects aren't listed¶
What you see: List projects is empty or errors.
Why it usually happens: Wrong URL/password, sync disabled on the server, or the CLI is not installed on the host.
What to check: Test the Source. URL for QFieldCloud is usually https://app.qfield.cloud/api/v1/. Ask an administrator if sync is enabled.
My Sync Job says "No changes"¶
What you see: Succeeded — No changes
Why it usually happens: The remote GeoPackage (QFieldCloud) or project version (Mergin Maps one-way) has not changed since the last successful sync.
What to check: Edit and upload in the field app, then Run Now. Two-way Mergin Maps will not use this status. See Sync problems.
PostGIS connection failed¶
What you see: Test or Run cannot reach the database.
Why it usually happens: Host/port/SSL, wrong password, database missing, or PostGIS extension not installed.
What to check: Test the saved Destination. Confirm you can connect with the same login from QGIS. GeoJibe does not create databases or enable PostGIS for you.