I don’t think there was an issue ticket associated with this forum thread.
I have taken your configuration and started Sync Gateway 1.2 using it, other than a missing ‘`’ back quote around the sync function (I suspect a paste error in the forum) I have not made any modifications. I created a ‘batch-test’ Couchbase Server bucket.
I used the following curl commands to validate that basic pull replication is functioning as expected, the first starts a continuous _changes feed.
curl -X GET http://couchbase_user:mobile@localhost:4984/batch-test/_changes?feed=continuous
This will block waiting for revision changes.
The second writes a document to the batch-test database via the Public REST API
curl -X PUT http://couchbase_user:mobile@localhost:4984/batch-test/doc1 -H "Content-Type: application/json" -d ' {"foo":"bar", "channels":["channel1"]}'
The continuous _changes feed sends the new revision in it’s response:
{"seq":3,"id":"doc1","changes":[{"rev":"1-47a34151ab9957a6772684233297aaea"}]}
In your configuration if you want to force user authentication set the GUEST user property “disabled”:“true”.
You can remove the “channels”:["*"], property from both users as this is a read only field, setting it in the configuration file has no effect.
If you are using Sync Gateway 1.2 can you set your logging property to “log”:["*"] to give maximum debugging info.
If you are still experiencing issues with pull replication, can you start a new thread and provide additional information such as the Sync Gateway logs for a period where you are starting pull replications and are pushing new document revisions to the database.
That should give us more information to help you resolve this issue.