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.

Maybe this is useful: https://source.chromium.org/chromium/chromium/src/+/main:components/autofill/core/browser/data_model/borrowed_transliterator.cc;l=54;drc=75b2dd916a3428f68e6c14a253f035b5a70b50ce

Would it be possible to just split the add/edit profile form (in chrome://settings/addresses) into first name, last name fields? We use a regex with the most common last names to identify spanish family names and split the "name" field accordingly. That means if you don't have any of those family names(like me) autofill will split your name incorrectly and there's no way of manually fixing it.  This is probably affecting quite a few users.

I believe this idea was discussed in the past, but discarded for several reasons:
- Fear of overloading the UI.
- Most users don't use the Autofill settings UI, so we need to be able to split names anyways.

But I agree that having no way of manually fixing it is suboptimal. Adding Matthias, who has more context on this issue.

Ideally, if the system would work as expected, users would only need to correct a wrong structure once. Unfortunately, this assumes that our field type predictions are always correct.
We have explored options to add controls to the settings in the past and we will revisit them. However, this is not trivial since most users will not even understand the concept of two last names and are likely to get confused. There are additional complications because it is not clear how the full name should be build from a first and a last name since the ordering is not the same for all countries. Additionally, Hispanic/Latinx names may have an additional conjunction between the first and the second last name which will make the settings even more complex.

This issue was migrated from crbug.com/chromium/1038337?no_tracker_redirect=1

[Monorail blocking: crbug.com/chromium/1008326]
[Monorail mergedwith: crbug.com/chromium/1058026]
[Monorail components added to Component Tags custom field.]