I forgot to mention that the build variants do compile the custom code
properly, so everything *but* the packageName seems to be working.
On Tuesday, February 18, 2014 3:08:30 AM UTC+9, Anthony Mandra wrote:
>
> I'm trying to port a typical free/pro build variant app to gradle. I've
> found that for some reason gradle will not apply the flavor packageName to
> the manifest.
>
> productFlavors {
> demo {
> packageName "com.domain.bar"
> }
>
> pro {
> packageName "com.domain.barpro"
> }
> }
>
> There are no errors during a build, but both builds retain the manifest
> defined "com.domain.bar". The 'pro' will fail to launch due to:
>
> *Error type 3 Error: Activity class
> {com.domain.barpro/com.domain.bar.Main} does not exist.*
>
> Any reason why the build would ignore the packageName, but the launch
> would attempt to process it? I've decompiled the app to confirm that the
> manifest remains unmodified by the gradle build.
>
--
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.
