You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Android:
2016-03-09T16:36:16.290+01:00 HTTP: #89: GET /ck/_session (as 13+18)
2016-03-09T16:36:16.290+01:00 HTTP+: #89: --> 200 (100.1 ms)
2016-03-09T16:36:17.065+01:00 HTTP: #90: GET /ck/_local/da07f67b0c421aa25c36b4618db86274e171e892 (as 13+18)
2016-03-09T16:36:17.066+01:00 HTTP: #90: --> 404 missing (0.7 ms)
2016-03-09T16:36:17.532+01:00 HTTP: #91: POST /ck/_changes (as 13+18)
2016-03-09T16:36:17.532+01:00 HTTP+: #91: --> 200 OK (0.0 ms)
2016-03-09T16:36:18.597+01:00 HTTP: #92: POST /ck/_bulk_get?revs=true&attachments=true (as 13+18)
2016-03-09T16:36:18.631+01:00 HTTP+: #92: --> 200 (34.1 ms)
So, it seems that the two version don' t work the same way.
IOS gets the changes and then write a local file on the server (probably the session id) while android first tries to get on session id, then a local file, and then gets the change. And never find the local which is created after replication by IOS !!!!
I don't understand anything. Why is the replication transaction so different between the two platforms ?
Really need help .........
The text was updated successfully, but these errors were encountered:
Stephanevincenza
changed the title
1.2.1- Replication issue with Android and couches sync
1.2.1- Replication issue with Android and couchbase sync
Mar 9, 2016
I've installed releases 1.3 for IOS and 1.2.1 for Android.
With the same code to start replication, I have always the same ERROR on Android.
[ERROR] : Sync: com.couchbase.lite.replicator.ReplicationInternal$4@424eece0 checkSessionAtPath() response: {authentication_handlers=[default, cookie], ok=true, userCtx={channels={!=1, _=218}, name=_**}}
The strange thing in the log of Couchbase SYNC ....
*With IOS *
2016-03-09T16:59:19.980+01:00 HTTP: #104: POST /ck/_changes
2016-03-09T16:59:19.980+01:00 HTTP: #104: --> 401 Login required (0.3 ms)
2016-03-09T16:59:20.227+01:00 HTTP: #105: POST /ck/_changes (as 13+18)
2016-03-09T16:59:20.228+01:00 HTTP+: #105: --> 200 OK (0.0 ms)
2016-03-09T16:59:20.403+01:00 HTTP: #106: POST /ck/_bulk_get?revs=true&attachments=true
2016-03-09T16:59:20.403+01:00 HTTP: #106: --> 401 Login required (5.8 ms)
2016-03-09T16:59:20.473+01:00 HTTP: #107: POST /ck/_bulk_get?revs=true&attachments=true (as 13+18)
2016-03-09T16:59:20.477+01:00 HTTP+: #107: --> 200 (8.2 ms)
2016-03-09T16:59:20.655+01:00 HTTP: #108: PUT /ck/_local/eba5f6d0ecc29033c1b934db2b063666550cdb1d
2016-03-09T16:59:20.656+01:00 HTTP: #108: --> 401 Login required (0.4 ms)
2016-03-09T16:59:20.688+01:00 HTTP: #109: PUT /ck/_local/eba5f6d0ecc29033c1b934db2b063666550cdb1d (as 13+18)
2016-03-09T16:59:20.688+01:00 HTTP+: #109: --> 201 (0.7 ms)
With Android:
2016-03-09T16:36:16.290+01:00 HTTP: #89: GET /ck/_session (as 13+18)
2016-03-09T16:36:16.290+01:00 HTTP+: #89: --> 200 (100.1 ms)
2016-03-09T16:36:17.065+01:00 HTTP: #90: GET /ck/_local/da07f67b0c421aa25c36b4618db86274e171e892 (as 13+18)
2016-03-09T16:36:17.066+01:00 HTTP: #90: --> 404 missing (0.7 ms)
2016-03-09T16:36:17.532+01:00 HTTP: #91: POST /ck/_changes (as 13+18)
2016-03-09T16:36:17.532+01:00 HTTP+: #91: --> 200 OK (0.0 ms)
2016-03-09T16:36:18.597+01:00 HTTP: #92: POST /ck/_bulk_get?revs=true&attachments=true (as 13+18)
2016-03-09T16:36:18.631+01:00 HTTP+: #92: --> 200 (34.1 ms)
So, it seems that the two version don' t work the same way.
IOS gets the changes and then write a local file on the server (probably the session id) while android first tries to get on session id, then a local file, and then gets the change. And never find the local which is created after replication by IOS !!!!
I don't understand anything. Why is the replication transaction so different between the two platforms ?
Really need help .........
The text was updated successfully, but these errors were encountered: