I don't know; you're the first to try this. You'll need to experiment to figure out what's going on. Something seems to be wrong at the NSURLConnection level; it's not able to connect.
—Jens > On Nov 12, 2014, at 9:43 PM, Br Achar <br.ac...@tcs.com> wrote: > > Jens, > We have tried syncing by removing the preflight connection check.We get a > request timeout error as in the logs as below. > > 2014-11-12 17:43:46.909 SampleApp.0.0.27jun[877:139523] Sync: > CBLReplication[from http://DeviceA.local.:58640/sampledb]: offline, progress > = 0 / 0, err: (null) > 2014-11-12 17:43:46.910 SampleApp.0.0.27jun[877:139523] Replication is > created with URL: http://DeviceA.local.:58640/sampledb > 2014-11-12 17:43:46.921 SampleApp.0.0.27jun[877:140111] Sync: > CBL_Puller[http://DeviceA.local.:58640/sampledb] STARTING ... > 2014-11-12 17:43:46.950 SampleApp.0.0.27jun[877:140111] Sync: > CBL_Puller[http://DeviceA.local.:58640/sampledb]: Going online > 2014-11-12 17:43:46.957 SampleApp.0.0.27jun[877:140111] Sync: > CBL_Puller[http://DeviceA.local.:58640/sampledb] Progress: set active = 1 > 2014-11-12 17:43:46.963 SampleApp.0.0.27jun[877:140111] SyncVerbose: > CBL_Puller[http://DeviceA.local.:58640/sampledb]: postProgressChanged (0/0, > active=1 (batch=0, net=1), online=1) > 2014-11-12 17:43:46.966 SampleApp.0.0.27jun[877:140111] SyncVerbose: > CBL_Puller[http://DeviceA.local.:58640/sampledb]: GET > _local/528a42c96259b10800762a87d9090da7cc844253 > 2014-11-12 17:43:46.999 SampleApp.0.0.27jun[877:140111] SyncVerbose: > CBL_Puller[http://DeviceA.local.:58640/sampledb]: postProgressChanged (0/0, > active=1 (batch=0, net=1), online=1) > 2014-11-12 17:43:47.006 SampleApp.0.0.27jun[877:139523] Sync: > CBLReplication[from http://DeviceA.local.:58640/sampledb]: active, progress = > 0 / 0, err: (null) > 2014-11-12 17:44:00.018 SampleApp.0.0.27jun[877:139523] > completedChangesCount: 0 changesCount: 0 > 2014-11-12 17:44:16.496 SampleApp.0.0.27jun[877:139523] DeviceA is stop > service > 2014-11-12 17:45:00.224 SampleApp.0.0.27jun[877:140111] > CBLRemoteJSONRequest[GET > http://DeviceA.local.:58640/sampledb/_local/528a42c96259b10800762a87d9090da7cc844253]: > Got error Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." > UserInfo=0x18263b90 > {NSErrorFailingURLStringKey=http://devicea.local.:58640/sampledb/_local/528a42c96259b10800762a87d9090da7cc844253, > > NSErrorFailingURLKey=http://devicea.local.:58640/sampledb/_local/528a42c96259b10800762a87d9090da7cc844253, > NSLocalizedDescription=The request timed out., NSUnderlyingError=0x181c2390 > "The request timed out."} > > Please advise us on what can be done since P2P bluetooth is unreliable one. > > > > Thanks & Regards > Lakshminarayana Achar B R > Tata Consultancy Services > Cell:- 9940021554 > Mailto: br.ac...@tcs.com > Website: http://www.tcs.com > ____________________________________________ > Experience certainty. IT Services > Business Solutions > Consulting > ____________________________________________ > > > -----Jens Alfke <jens.al...@gmail.com> wrote: ----- > To: mobile-couchbase@googlegroups.com > From: Jens Alfke <jens.al...@gmail.com> > Date: 11/12/2014 11:07PM > Cc: phanitej...@tcs.com, rubha.selva...@tcs.com, br.ac...@tcs.com, > kanya.va...@tcs.com > Subject: Re: CBLReplication with only Peer-Peer WiFi and no Bluetooth > > > >> On Monday, October 20, 2014 11:11:50 AM UTC-7, Jens Alfke wrote: >> >>> On Oct 20, 2014, at 2:47 AM, Lakshminarayana Achar <brl...@gmail.com> wrote: >>> >>> Looks like a reachability issue. >>> Is there something that can be done from our end or your end to fix the >>> issue ? >> >> Weird. Yes, from the logs it looks like the SCNetworkReachability API isn't >> behaving correctly with WiFi. Which is the opposite of what I'd expect; >> since IP-over-Bluetooth is unusual, I'd expect that to be the configuration >> with problems. > > After some discussion with Quinn of Apple's developer tech support, it sounds > like (a) SCNetworkReachability isn't returning the correct results in the > case of an ad-hoc (no base station) WiFi network, and (b) one shouldn't rely > on reachability to preflight making a connection — instead we should try to > connect regardless. > > It looks like despite all this discussion no bug report has been filed, so > I'll create one now. > > —Jens > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/A5CDA974-7D2E-46BC-8766-A52661AC027B%40mooseyard.com. For more options, visit https://groups.google.com/d/optout.
