Ha, whops, didn't realize the new manifest merging system was disabled by
default, it's working as expected now. Disregard this.
For anyone else running into similar problems:
android {
useOldManifestMerger false
}
On Wednesday, June 4, 2014 3:42:51 PM UTC-7, Adam Brown wrote:
>
> I've got a use case that looks like it may not be supported, so I thought
> I'd post it here and see if it's something that people think could be
> useful as a feature.
>
> I'm setting up the Android monkey to do some soak testing of my app, and I
> need it to only hit certain activities (*to prevent it from signing out
> and a few other things*). In order to do this, I need the Activities I do
> want it to hit, to have Intent filters specifying categories which the
> Monkey can look for.
>
> I don't really want these in my production Manifest. So ideally, I would
> be able to specify entries in my debug manifest for each Activity, and have
> them override the ones defined in my main manifest. Even better would be if
> it were cascading, where I could just define what I wanted different in the
> debug manifest, and it'd take the rest of the definition from the main
> Manifest.
>
--
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/d/optout.
