Assigned
Status Update
Comments
ja...@gmail.com <ja...@gmail.com> #2
Building with eclipse also fails for me since upgrading to r21.
mi...@gmail.com <mi...@gmail.com> #3
Do some of your libraries and/or the app share the same package name? this could trigger this bug I think.
pa...@gmail.com <pa...@gmail.com> #4
Oh btw, building with eclipse now also fails for me. Seems i hadn't fully upgraded the Plugin to v21 by the time.
Yes, our library projects all share the same package name and we use the manifest merger.
Yes, our library projects all share the same package name and we use the manifest merger.
br...@gmail.com <br...@gmail.com> #5
It happens when not using manifest merger too.
ja...@gmail.com <ja...@gmail.com> #6
We have made a fix to better support setup when libraries share package name.
Note that it will only work if *all* libraries share the same package name. If only some do, then the build will fail.
We will be releasing this shortly.
Note that it will only work if *all* libraries share the same package name. If only some do, then the build will fail.
We will be releasing this shortly.
ra...@gmail.com <ra...@gmail.com> #7
The issue is still there in ADT 21.0.1 (platform tools 16.0.1) when building with Ant.
It is fixed in ADT, though, so Eclipse builds fine.
I attached a ZIP file containing a simple project setup that leads to this error.
It seems that Ant generates another Manifest.java file in the final project which is not the case for ADT.
There is also *another* error when multiple projects define permissions.
For example, in my project setup, if LibA defines
<permission android:name="com.example.adttest.permission.READ_PROVIDER" />
and LibB defines
<permission android:name="com.example.adttest.permission.READ_OTHER_PROVIDER" />
both ADT and Ant will fail to build.
It is fixed in ADT, though, so Eclipse builds fine.
I attached a ZIP file containing a simple project setup that leads to this error.
It seems that Ant generates another Manifest.java file in the final project which is not the case for ADT.
There is also *another* error when multiple projects define permissions.
For example, in my project setup, if LibA defines
<permission android:name="com.example.adttest.permission.READ_PROVIDER" />
and LibB defines
<permission android:name="com.example.adttest.permission.READ_OTHER_PROVIDER" />
both ADT and Ant will fail to build.
al...@android.com <al...@android.com>
ma...@gmail.com <ma...@gmail.com> #8
I'll check this, thanks for the project.
[Deleted User] <[Deleted User]> #9
[Comment deleted]
mi...@gmail.com <mi...@gmail.com> #10
Are there any fixes yet? Still have this problem in ADT 21.1.0
[Deleted User] <[Deleted User]> #11
Still happening with ADT 22 while Gradle works fine.
[Deleted User] <[Deleted User]> #12
I had a very similar issue. I had to:
1. Make all libraries and projects use different package name in their manifest
2. Delete all bin/ directories
3. Delete all gen/ directories
ALL of these steps were necessary. I had different "Multiple dex files define ..." errors depending on how clean my build environment was.
To be really specific, as long as the multiple classes.jar files contain duplicate items, dex will complain. With step 1-2-3 above I could eliminate all duplicates, all my classes.jar files contain distinct items.
I hope this helps.
1. Make all libraries and projects use different package name in their manifest
2. Delete all bin/ directories
3. Delete all gen/ directories
ALL of these steps were necessary. I had different "Multiple dex files define ..." errors depending on how clean my build environment was.
To be really specific, as long as the multiple classes.jar files contain duplicate items, dex will complain. With step 1-2-3 above I could eliminate all duplicates, all my classes.jar files contain distinct items.
I hope this helps.
[Deleted User] <[Deleted User]> #13
Thanks -Janos.Gyerik your suggestion worked for me...
bo...@gmail.com <bo...@gmail.com> #14
I still find it strange that permission-distribution to multiple library projects with same package name is not supported. But as this even continues with gradle (and afaik is even enforced more strictly there) it seems the way to go.
Just for reference if you are in need for the old "build-tools" i think they can be found here:http://dl-ssl.google.com/android/repository/platform-tools_r14-linux.zip
Just for reference if you are in need for the old "build-tools" i think they can be found here:
[Deleted User] <[Deleted User]> #15
Thank you for reporting this issue. At this time it appears this feedback is no longer relevant with the latest version of Android Studio. If you continue to experience this issue please open a new bug and we can reinvestigate
ma...@gmail.com <ma...@gmail.com> #16
Any date to the release of this feature? Working with VectorDrawables is awesome and let us have an IconKit but this little impediment make it not perfect
ja...@gmail.com <ja...@gmail.com> #17
Voting +1 for this feature.
mo...@gmail.com <mo...@gmail.com> #18
Voting +1 for this feature.
m....@gmail.com <m....@gmail.com> #19
voting +1 for this feature
de...@gmail.com <de...@gmail.com> #20
Voting +1 for this feature.
me...@gmail.com <me...@gmail.com> #21
Voting +1 for this feature.
kr...@gmail.com <kr...@gmail.com> #22
+1 from me. I really need this feature.
su...@gmail.com <su...@gmail.com> #23
+1 from me. I've to fallback my implementation to webview because of this graphic inconsistency.
ar...@connectmedica.com <ar...@connectmedica.com> #24
Voting +1 for this feature.
ia...@gmail.com <ia...@gmail.com> #25
Voting +1 for this feature.
ke...@pinxterapp.com <ke...@pinxterapp.com> #26
Voting +1 for this feature.
ni...@google.com <ni...@google.com>
[Deleted User] <[Deleted User]> #27
Not being able to set a proper dark or light statusbar/toolbar icon color is breaking our app color design very bad.
+1 for this feature.
+1 for this feature.
ja...@gmail.com <ja...@gmail.com> #28
Voting +1 for this feature.
[Deleted User] <[Deleted User]> #29
Estoy de acuerdo con este comentario, es molesto cuando el diseñador te levanta la mano porque no le convence el contraste de los colores y te es imposible responder con fundamento y suplir los criterios. Sería genial poder personalizar más esta sección.
ru...@gmail.com <ru...@gmail.com> #30
This has been an issue for 6 years now. Why isn't Google dealing with it? If I'm to use Custom Tabs, I need to be able to change the toolbar text and color at will.
sa...@gmail.com <sa...@gmail.com> #31
ช่วยแก้ไข browser ให้ผมหน่อยครับ
Description
However, for my app, the derived colors for both are noticeably different than the rest of my application. While the functionality of custom tabs is winning over the designer, they are not happy with the visual result.
Therefore, I'd like to be able to specify the status bar color to use with the custom tab (ie the primaryColorDark from my application). Seems reasonable if the developer doesn't specify a status bar color it uses the derived color as it does today.
As well I'd like to control the icon tint in the tool bar for the default "close" and "overflow" icons. While, specifying my own bitmap works around the "close" icon, the overflow icon tint is still controlled by the custom tab and may not match the overall theme.