I was waiting to have the time to produce a minimal working project with the problem and i have been unable to reproduce it. It is working correctly now.
I am sure that i performed a project clean when the problem appeared so it was not an incremental build problem either. Maybe it had something to do with maven / gradle caches, i do not know, but well, now it works :) Thanks! On Tuesday, February 18, 2014 10:13:37 AM UTC+1, Roman Mazur wrote: > > I use the same approach and do not experience any problems with any build > type. > > On Monday, 17 February 2014 13:53:35 UTC+2, Juan Ramón González wrote: >> >> Hi, there seems to be a bug in the android gradle plugin (0.8.3 at least) >> when generating the merged manifests from libraries and app project. >> >> I am using Crashlytics in several projects and it requires a meta tag in >> the manifest like this: >> >> <meta-data >> android:name="com.crashlytics.ApiKey" >> android:value="API_KEY"/> >> >> Since the api key is the same for all projects where you include >> Crashlytics i moved that meta tag to the manifest of one of my libraries. >> >> This works perfectly with release builds and the manifest of the apps are >> properly merged and show the Crashlytics meta tag, but the manifest of the >> debug builds does not include it leading to a crash in the build process. >> >> Regards, >> Juan R, Gonzalez >> >> >> >> -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
