Detect that user is not valid in replication

Mobile
12

Your db config has no users object, so by default guest access isn’t enabled.

Correct, our ‘edc’ bucket does not have a Guest user, the other two buckets do, could that be causing the issue? We will be removing these as they were just for testing purposes.

{
  "Interface": "xxx.net:4984",
  "AdminInterface": "xxx.net:4985",
  "CORS": {
    "Origin": [
      "*"
    ],
    "LoginOrigin": [
      "*"
    ],
    "Headers": [
      "Content-Type"
    ],
    "MaxAge": 0
  },
  "Log": [
    "HTTP+",
    "Changes+",
    "CRUD+",
    "Bucket",
    "Auth",
    "Feed+",
    "Cache+",
    "Access",
    "Events+"
  ],
  "LogFilePath": "D://Couchbase//log//SG.log",
  "Databases": {
    "edc": {
      "server": "http://xxxx.net:8091",
      "pool": "default",
      "bucket": "edc",
      "username": "edc",
      "password": "edcnextgen",
      "name": "edc",
      "sync": "function(doc) {channel(doc.channels);}",
      "event_handlers": {
        "document_changed": [
          {
            "filter": "function(doc) { if (doc.data.assessmentStatus && doc.data.docType == \"visit\") { return true; } return false; }",
            "handler": "webhook",
            "url": "xxxx.net:8181/cb-rs/chaIntake"
          }
        ]
      }
    },
    "edc_extracts": {
      "server": "xxxx.net:8091",
      "pool": "default",
      "bucket": "edc_extracts",
      "name": "edc_extracts",
      "sync": "function(doc) {channel(doc.channels);}",
      "users": {
        "GUEST": {
          "name": "",
          "admin_channels": [
            "*"
          ],
          "all_channels": null
        }
      }
    },
    "sync_gateway": {
      "server": "xxxx.net:8091",
      "pool": "default",
      "bucket": "sync_gateway",
      "name": "sync_gateway",
      "sync": "function(doc) {channel(doc.channels);}",
      "users": {
        "GUEST": {
          "name": "",
          "admin_channels": [
            "*"
          ],
          "all_channels": null
        }
      }
    }
  }
}

To my knowledge no one has updated the bucket configuration via the ADMIN.