Infeasible
Status Update
No update yet.
Comments
ch...@google.com
Please fix this!!!. We have quite a few apps that cannot use GCM because of this.
sc...@gmail.com
This should have a "high" priority, not a "medium" priority. The reason being that you cannot change the package name for apps already deployed to the app store. This means that any apps that have already been deployed with upper case package name are unable to use GCM. :-(
ch...@google.com
je...@google.com
This goes back to an issue with C2DM. It did not allow the package name permission to start with a capital letter either. Since Android allows the package name to start with a capital letter, this permission should be able to as well.
ta...@planner5d.com
Here is the excerpt from android package name documentation :
http://developer.android.com/guide/topics/manifest/manifest-element.html
"A full Java-language-style package name for the application. The name should be unique. The name may contain uppercase or lowercase letters ('A' through 'Z'), numbers, and underscores ('_'). However, individual package name parts may only start with letters."
Upper case letters should be ok.
"A full Java-language-style package name for the application. The name should be unique. The name may contain uppercase or lowercase letters ('A' through 'Z'), numbers, and underscores ('_'). However, individual package name parts may only start with letters."
Upper case letters should be ok.
ta...@planner5d.com
After doing a little more digging, the original post has the best description in the correct behavior. Currently ANY permission must not begin with a capital letter if and only if there is a dot operator inside of it. Permissions should be able to be created with capitalized names.
je...@google.com
Isn't there a way to do this yet?
It's really anoying for everyone, users and developers, to do a new app just for this issue
It's really anoying for everyone, users and developers, to do a new app just for this issue
Description
This is reproducible under the following conditions for us.
Android gradle plugin 1.5.0 or 2.0.0-beta2
minSdkVersion is 21 or greater. Setting minSdkVersion to 19 makes the issue go away.
The device or emulator is running API 21 or 22. It doesn't seem to be a problem in API 23
100 or more classes.dex files are packaged in the apk.
Classes that are included in classes(100+).dex throw a ClassNotFoundException or NoClassDefFoundError when they are accessed in the app.
Classes that are in classes.dex or classes(2-99).dex work just fine when referenced.