http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/CBMI-72 Couchbase Mobile iOS Couchbase fails to start. <br/> This issue can be replicated by checking-out the latest CouchbaseMobile demo on github: <br/> <a href="https://github.com/couchbaselabs/iOS-Couchbase-Demo">https://github.com/couchbaselabs/iOS-Couchbase-Demo</a> <br/> <br/> In order to reproduce this error, the device must not have been enabled for development through Xcode. <br/> The moment you press &quot;Use for Development&quot; in Xcode, and then run the app, Couchbase successfully starts. <br/> <br/> The log messages seen when running the application are: <br/> Mar 13 16:59:00 unknown GrocerySync[428] : ------ application:didFinishLaunchingWithOptions: <br/> Mar 13 16:59:00 unknown kernel[0] : launchd[428] Builtin profile: container (sandbox) <br/> Mar 13 16:59:00 unknown kernel[0] : launchd[428] Container: /private/var/mobile/Applications/F8D6B51E-8CED-42B0-907B-F94378E2403A [69] (sandbox) <br/> Mar 13 16:59:30 unknown GrocerySync[428] : Couchbase: Error: No startup notification from server engine <br/> <br/> Even if debug logging is turned on via the default_ios.ini file, still no more detailed couch logs are shown. iOS 5.1 CBMI-72

CouchbaseMobile startup failure on iOS 5.1

Bug Critical Open Unresolved J Chris Anderson Chaise Hocking Tue, 13 Mar 2012 01:44:18 -0500 Tue, 13 Mar 2012 20:37:32 -0500 2.0 SDK 4 4 I would like to escalate this to a blocker. &gt; the device must not have been enabled for development through Xcode. <br/> <br/> Is that permanent? Is there a way to reproduce this with a device that&#39;s already been development-enabled, short of wiping and re-installing the OS? I have similar problem with an app that uses CouchBase on iOS 5.1. My app works when the device is connected to my development machine. All of the custom code was inspected and there are no memory leaks. <br/> The app crashes at start up only after I reboot the ios5.1 device and when the device is not connected to development machine. <br/> The app works just fine on ios5.0.0.1 and 4.3. <br/> <br/> ----------------------------------- <br/> Some details from the crash log: <br/> ----------------------------------- <br/> <br/> Incident Identifier: 0E3400D5-802F-4508-AD73-414E3CA608AB <br/> CrashReporter Key: c35154e21347780a3a93befed1dbd11b41b5a150 <br/> Hardware Model: iPad2,1 <br/> Process: halfteam [78] <br/> Path: /var/mobile/Applications/0F8E0ACA-D374-4673-AC46-B0811B6974D8/halfteam.app/halfteam <br/> Identifier: halfteam <br/> Version: ??? (???) <br/> Code Type: ARM (Native) <br/> Parent Process: launchd [1] <br/> <br/> Date/Time: 2012-03-13 11:24:39.012 -0400 <br/> OS Version: iPhone OS 5.1 (9B176) <br/> Report Version: 104 <br/> <br/> Exception Type: EXC_CRASH (SIGABRT) <br/> Exception Codes: 0x00000000, 0x00000000 <br/> Crashed Thread: 0 <br/> <br/> Last Exception Backtrace: <br/> 0 CoreFoundation 0x33eb388f __exceptionPreprocess + 163 <br/> 1 libobjc.A.dylib 0x329a5259 objc_exception_throw + 33 <br/> 2 CoreFoundation 0x33eb3789 +[NSException raise:format:] + 1 <br/> 3 Foundation 0x32df93a3 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 91 <br/> 4 halfteam 0x000a4425 -[AppDelegate couchbaseMobile:failedToStart:] (AppDelegate.m:62) <br/> 5 halfteam 0x000cf2f9 -[CouchbaseMobile startupTimeout] + 89 <br/> 6 Foundation 0x32e2b933 __NSFireDelayedPerform + 415 <br/> 7 CoreFoundation 0x33e87a33 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 15 <br/> 8 CoreFoundation 0x33e87699 __CFRunLoopDoTimer + 365 <br/> 9 CoreFoundation 0x33e8626f __CFRunLoopRun + 1207 <br/> 10 CoreFoundation 0x33e094a5 CFRunLoopRunSpecific + 301 <br/> 11 CoreFoundation 0x33e0936d CFRunLoopRunInMode + 105 <br/> 12 GraphicsServices 0x33387439 GSEventRunModal + 137 <br/> 13 UIKit 0x35afee7d UIApplicationMain + 1081 <br/> 14 halfteam 0x000a405f main (main.m:14) <br/> 15 halfteam 0x000a4018 start + 40 <br/> ..... <br/> This appears to be happening to us as well ... and it&#39;s a *showstopper* for our app, obviously. <br/> <br/> CouchbaseMobile sometimes does not start up on launch when running on 5.1 ... same &quot;Couchbase: Error: No startup notification from server engine&quot; message ... our testing supports the idea that it works okay when connected to Xcode and the phone is enabled for development, and it seems to not work when not connected to Xcode. It doesn&#39;t seem to matter whether the debugger is running, though, because I&#39;ve launched it *manually* while connected to Xcode (not by hitting the Run button in Xcode, so no debugger running) and Couchbase still failed to start. <br/> <br/> We were just about to submit to Apple for review! So, good thing we found this before the app was in the wild .. but it would obviously be good to get this fixed asap. <br/> <br/> Let me know if you need any other information to help debug it. <br/> <br/> Thanks! Oops .. let me edit one sentence in my last comment: <br/> <br/> &quot;...because I&#39;ve launched it *manually* while connected to Xcode (not by hitting the Run button in Xcode, so no debugger running) and Couchbase STARTED NORMALLY.&quot; I can report a similar problem using couchbase mobile 2.0.1 on iOS 5.1 <br/> <br/> iPhone attached to development computer and run from Xcode, app runs as expected <br/> <br/> Mar 13 21:51:48 unknown miituu[90] &lt;Warning&gt;: Couchbase: Found db files in ~/Documents, so using that as rootDirectory <br/> Mar 13 21:51:48 unknown miituu[90] &lt;Warning&gt;: -[MiituuAppDelegate application:didFinishLaunchingWithOptions:] [Line 85] Documents Directory : /var/mobile/Applications/AE80CECD-22D3-42FD-8511-B885C028AC17/Documents <br/> Mar 13 21:51:48 unknown miituu[90] &lt;Warning&gt;: ------ applicationDidBecomeActive <br/> <br/> iPhone restarted and couchbase fails to start. <br/> <br/> Mar 13 21:52:18 unknown miituu[90] &lt;Warning&gt;: Couchbase: Error: No startup notification from server engine <br/> Mar 13 21:52:18 unknown miituu[90] &lt;Warning&gt;: -[MiituuAppDelegate couchbaseMobile:failedToStart:] [Line 264] OMG: Couchbase couldn&#39;t start! Exiting! <br/> Mar 13 21:52:18 unknown miituu[90] &lt;Warning&gt;: -[MiituuAppDelegate couchbaseMobile:failedToStart:] [Line 265] The operation couldn’t be completed. (Couchbase error 2.) : (null) <br/> Mar 13 21:52:18 unknown miituu[90] &lt;Warning&gt;: -[MiituuAppDelegate couchbaseMobile:failedToStart:] [Line 266] The operation couldn’t be completed. (Couchbase error 2.) : (null) <br/> Hi Jens. Could you give us a status on this bug when you have a chance? Just wondering if you all are working on it yet, and if you have any sense yet of whether it&#39;s going to be a relatively quick fix. We&#39;re under some pressure to launch asap (investors and such), so it would be good to have some sort of estimate of how long it might be, if at all possible. <br/> <br/> Thanks again! &gt;Is that permanent? Is there a way to reproduce this with a device that&#39;s already been development-enabled, short of wiping and re-installing the OS? <br/> <br/> Hi Jens, <br/> Yes it is permanent. <br/> Though it is relatively fast to reset the device without needing to re-install the os. If you use: <br/> &gt;Settings &gt;Reset &gt;Erase All Content and Settings <br/> <br/> This will cause couchbase to consistently and repeatedly fail. <br/> So far I have not been able to reproduce the issue the issue once the device has been &quot;enabled for development&quot;. <br/> Using &quot;Use For Development&quot; will enable a previous install of the same app to begin working. The problem appears to stem from Erlang calling printf. As far as I can tell, this is hanging — maybe because stdout isn&#39;t attached to anything and locks up when its buffer fills up? All I know is that, if I use freopen to redirect stdout to a file, it makes the problem go away. <br/> I&#39;m asking on Apple&#39;s mailing lists to see if anyone knows anything about this issue. But the good news is that I can check in a two-line patch that makes it go away (even if I don&#39;t know exactly why.) <br/> <br/> &gt; Yes it is permanent. <br/> <br/> Really? I was able to reproduce it simply by shutting down and restarting the device. After that, the app will lock up, until the next time the device is tethered to Xcode. That&#39;s great news Jens! Looking forward to trying out the fix. <br/> <br/> Are you going to post a new binary of couchbase mobile as well as checking in the patch? Compiling CBM from source was a bit tricky, as I recall. Out for review: <br/> <a href="http://review.couchbase.org/#change,13924">http://review.couchbase.org/#change,13924</a> Patrick: Yes, we will post a new build. Hopefully later today or tomorrow. Thank you so much Jens! You&#39;re like Superman flying in and saving the day! :-) <br/> <br/> So will the new binary be on the CBM wiki page? Is there a way to be notified when it&#39;s available? For anyone who cannot wait for a new Couchbase mobile build, there is no reason why you can&#39;t put Jens&#39;s fix in your own application code. <br/> <br/> NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES); <br/> NSString *logDirectory = [[paths objectAtIndex:0] stringByAppendingPathComponent:@&quot;Logs&quot;]; <br/> <br/> if(![[NSFileManager defaultManager] fileExistsAtPath:logDirectory isDirectory:NULL]) <br/> [[NSFileManager defaultManager] createDirectoryAtPath:logDirectory withIntermediateDirectories:YES attributes:nil error:NULL]; <br/> <br/> freopen([[logDirectory stringByAppendingPathComponent:@&quot;stdout.log&quot;] UTF8String], &quot;w+&quot;, stdout); Actually you could do an even simpler fix if you don&#39;t care about stdout at all: <br/> &nbsp;&nbsp;&nbsp;&nbsp;freopen(&quot;/dev/null&quot;, &quot;w&quot;, stdout); <br/> <br/> I&#39;m finding that some other developers are running into this issue too, although I haven&#39;t found anyone who knows exactly what&#39;s going on: <br/> <a href="http://bugs.freepascal.org/view.php?id=21440">http://bugs.freepascal.org/view.php?id=21440</a> <br/> <a href="http://blog.xamarin.com/2012/03/11/monotouch-and-ios-5-1/">http://blog.xamarin.com/2012/03/11/monotouch-and-ios-5-1/</a> <br/> Thanks, Chaise -- <br/> The proposed solution worked for me. Our app was approved a week ago and we are about to go live so this was a truly urgent issue... <br/> <br/> Highly appreciated! Rank 9491