Hi Jessica,

The 1.0.2 Couchbase-lite update broke our build. And it took me an hour to 
work out why :(
Somewhere between the 1.0.0 -> 1.0.2 update, Couchbase-lite started using 
DDLog from CocoaLumberjack. Unfortunately, because this is not listed as a 
Pod-level dependency, but provided directly in one of the Couchbase-lite 
frameworks, this creates a duplicate symbol at runtime:

*objc[285]: Class DDLog is implemented in both 
/private/var/mobile/Containers/Bundle/Application/E6E25213-1BC1-4767-9BB2-0DE91DF06256/my.app/myapp
 
and 
/private/var/mobile/Containers/Bundle/Application/E6E25213-1BC1-4767-9BB2-0DE91DF06256/my.app/myapp.
 
One of the two will be used. Which one is undefined.*
... and causes the app to crash as soon as DDLog is called.

Please don't define DDLog* symbols directly in Couchbase frameworks -- 
instead, update your .podspec to depend upon the CocoaLumberjack pod.

thanks
Tim


On Wednesday, August 27, 2014 11:18:05 PM UTC+2, Jessica Liu wrote:
>
> Hi community, in addition to our recent patch release for Couchbase Lite 
> iOS and Android, we have a 1.0.2 update for Sync Gateway that you can 
> download today here: www.couchbase.com/download#cb-mobile
>
> A major fix that was included was rectifying a continuous replication loop 
> that occurred when a new user was manually added to a channel. This issue 
> alongside some fixes concerning bucket shadowing, short passwords, and 
> error handling, were addressed in 1.0.2. A full list highlighting the fixes 
> going into 1.0.2 is available here: 
> http://developer.couchbase.com/mobile/develop/references/sync-gateway/release-notes/1.0.2/index.html
>
> Thank you.
> - Jessica
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/f4f9ab29-8b8e-4589-abb7-bc68f4fcdbe5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to