IssueTracker

Please fix this!!!. We have quite a few apps that cannot use GCM because of this.

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. :-(

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.

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.

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.

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

news ?

DO AGREE...the same requirements as for Java package name should be used for permissions!

결론이 난건가요?

Any Update on this?
I need this feature too.
if the App is already in Store with the packagename "Myapplication.com" and you rename this Line: <permission android:name="myapplication.com.permission.C2D_MESSAGE" android:protectionLevel="signature" /> to a lower case letter, then it will work, but only for Devices with Android 4+.

Please fix this!

You probably cannot fix this retroactively for devices that are already running non-supporting versions of Android, since there's no way to force an update in general.  So to me it seems that the fix would be for the GP store to allow apps to rename their packages on an update from mixed case to all lower case, so long as nothing else changes and so long as there was not already another app with the resulting lower-case name.  The store, being in the cloud, can fix this for almost everyone (except some very unfortunate hypothetical person who decided to have two apps with package names only distinguished by case).  That should handle 99.9 percent of the cases.

This bug has been marked as obsolete but there is no resolution provided.

still opened and still no solution to this after years.

Jeeeeeeez this is such a weird bug.

Hello all.

I am using cyanogenmod, which is Android recompiled and packaged with improvements.

Sometimes those improvements get back into the mainstream Android code.
So I filed a request for this behaviour being fixed on the cyanogenmod issue tracking.
The more it gets starred, the more likely the developers will take it into account realizing it is an issue for many; so I would please encourage you all to get there and star that.
In the end, it could be fixed and entering the regular android baseline. It will take plenty of time even in the most optimistic circumstances, but it would still be awesome to have that fixed even if not in a short time.

This very issue here was just linked in that bug tracking system by the way.

Here's the link:

http://code.google.com/p/cyanogenmod/issues/detail?id=4639

Thanks!

I also have this problem on my Nexus S running ICS, it was fine on 2.3.7 but since android 4 update sms name/numbers are not recognised. I can search for a name then send a text but I get a reply from the number and not the name I just sent! If I go into address book and change the 07 (uk mobile prefix) to +44 the unknown number changes to the correct name.But I am not going to do this to the hundreds of mobile numbers I have stored just for a software glitch. Patch It Google!!

Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO.