Fixed
Status Update
Comments
co...@gmail.com <co...@gmail.com> #2
Please fix this!!!. We have quite a few apps that cannot use GCM because of this.
gk...@google.com <gk...@google.com> #4
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.
[Deleted User] <[Deleted User]> #5
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.
co...@gmail.com <co...@gmail.com> #6
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.
co...@gmail.com <co...@gmail.com> #7
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
na...@gmail.com <na...@gmail.com> #9
DO AGREE...the same requirements as for Java package name should be used for permissions!
br...@gmail.com <br...@gmail.com> #11
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!
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!
pr...@gmail.com <pr...@gmail.com> #12
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.
ji...@gmail.com <ji...@gmail.com> #13
This bug has been marked as obsolete but there is no resolution provided.
ya...@danielzrihen.co.il <ya...@danielzrihen.co.il> #14
still opened and still no solution to this after years.
an...@gmail.com <an...@gmail.com> #15
Jeeeeeeez this is such a weird bug.
ji...@mymusictaste.com <ji...@mymusictaste.com> #17
still happening problem
al...@cazisoft.com <al...@cazisoft.com> #18
Not fixed still not able to get the active sheet name after modifying e.g. filter. It always reports the first sheet.
ol...@imagination.com <ol...@imagination.com> #19
This error is still not fixed.
ds...@golocalpromos.com <ds...@golocalpromos.com> #20
How many year have to wait? Please fix it ! Tks.
gs...@gmail.com <gs...@gmail.com> #21
Hey, we are here. are you?
sh...@gmail.com <sh...@gmail.com> #22
is it really fixed yet? i still got the error
mg...@hcn-inc.com <mg...@hcn-inc.com> #23
Fixed doesn't mean deployed... do we have to wait another 10 years for the deployment?
Description
not already been reported.
Please provide a short description of the issue:
When I get the active sheet in the onChange trigger, I have just the first sheet on my spreadsheet.
Please provide a small sample script that reliably reproduces the issue.
The sample should run as-is or with minimal setup, without external
dependencies.
function onChange(e) {
Logger.log("Appel de onchange avec : "+e.changeType)
Logger.log(SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getName())
if ( e.changeType == "INSERT_ROW" || e.changeType == "REMOVE_ROW"){
//MAJFormule()
}
}
What steps will reproduce the problem?
1. Create a spreasheet with 12 or more sheets OR Copy the spreadsheet :
2. Add a row or remove one on a sheet, but not the first
3. See in log (ctrl+enter) the active sheet given by the first sheet only
What is the expected output? What do you see instead?
I expect to see the correct active sheet, not the first
What is the project key (found under "File > Project properties")? The
project key does not give the Apps Script team access to your source
code or data. We use it to look up debug information about your script.
Mnl9Uc8-amn4U6dnGWK6y4N5EmEfOErDz
Please provide any additional information below.
To subsequent readers: If you are also experiencing this issue, please
click the star next to the issue number. We prioritize issues with the
most stars.