Bug P2
Status Update
Comments
bc...@opnw.com <bc...@opnw.com> #2
It seems like it's also not restarted when being killed due to a low memory condition. This is a serious issue!
[Deleted User] <[Deleted User]> #3
Same as 63618 issue reported before.
bc...@opnw.com <bc...@opnw.com> #4
Ruins battery notifications
[Deleted User] <[Deleted User]> #5
Had to stop using this. Too bad, loved it.
ry...@google.com <ry...@google.com> #6
Why is this rated a "Priority-Small" ? This makes all applications that use a background service useless
al...@gmail.com <al...@gmail.com> #7
Same for apps showing widgets! Even those apps Google rated best apps from best developers, are affected by this!
Can only be a mistake. Or its like killing all Play Store apps, except games. Could it be intentional? I can't believe it yet.
Can only be a mistake. Or its like killing all Play Store apps, except games. Could it be intentional? I can't believe it yet.
[Deleted User] <[Deleted User]> #9
Yes, the service stops in any moment. I think it's a big problem. In lower versions no problem with the background service.
[Deleted User] <[Deleted User]> #10
Same issues here. This is indeed a serious problem.
su...@gmail.com <su...@gmail.com> #11
I'm having similar issues. Real problems also with the notificationlistener service just stopping sending notifications to apps without a reboot.
ry...@google.com <ry...@google.com> #12
Must be fixed!
[Deleted User] <[Deleted User]> #13
[Comment deleted]
al...@gmail.com <al...@gmail.com> #14
[Comment deleted]
al...@gmail.com <al...@gmail.com> #15
This is a significant problem. START_STICKY services are being killed by the Android system (presumably because resources are low?) and are never restarted. This behavior has been observed on multiple Nexus 5 devices running Android 4.4.2.
Also, START_STICKY services attached to activities that are cleared out of the Recent Apps list are also being killed and never restarted (see issue 36949180 ). This behavior has been observed on multiple Nexus 5 devices running Android 4.4, 4.4.1, and 4.4.2.
Also, START_STICKY services attached to activities that are cleared out of the Recent Apps list are also being killed and never restarted (see
al...@gmail.com <al...@gmail.com> #16
I have same problem with app widgets, my app widget has a back-end service which on 4.4.2 stops and never restarts.
al...@gmail.com <al...@gmail.com> #17
Confirmed fir the Nexus 4 as well.
Op 29 dec. 2013 08:07 schreef <android@googlecode.com>:
Op 29 dec. 2013 08:07 schreef <android@googlecode.com>:
ry...@google.com <ry...@google.com> #18
Making the service a foreground service with startForeground() along with START_STICKY appears to circumvent this bug. This might not be the most appropriate path for all apps though, as it (appropriately) requires a notification icon to be displayed in exchange for the higher system resources priority.
[Deleted User] <[Deleted User]> #19
This needs to be prioritized!
[Deleted User] <[Deleted User]> #20
Only Google apps aren't affected by this bug, really need to be prioritized!!
[Deleted User] <[Deleted User]> #21
In Nexus 7 (upgraded to 4.4.2), service is running in the background but not bring to front.
Very high priority issue!! Please solve ASAP..
Very high priority issue!! Please solve ASAP..
al...@gmail.com <al...@gmail.com> #22
Same issue with all my devices running KitKat!! This needs a fast fix!
[Deleted User] <[Deleted User]> #23
Please
al...@gmail.com <al...@gmail.com> #24
Been experiencing this issue on my Nexus 5 and Nexus 7 for all kinds of apps. The background processes are killed and never restart!
ac...@gmail.com <ac...@gmail.com> #25
Please fix this problem
da...@gmail.com <da...@gmail.com> #26
Got to wonder how Google get around this bug, must have secret APIs...
ac...@gmail.com <ac...@gmail.com> #27
please fix!
gc...@160over90.com <gc...@160over90.com> #28
[Comment deleted]
ma...@gutsend.com <ma...@gutsend.com> #29
Wtf? If you know this bug, but to be fixed it should be voted for? Shouldn't developers fix all the bugs?
ry...@google.com <ry...@google.com>
ma...@gmail.com <ma...@gmail.com> #30
@#28
They are making a contest for bug which will annoy dev most. Share it on FB or G+ to convince people to vote for OUR bug!
They are making a contest for bug which will annoy dev most. Share it on FB or G+ to convince people to vote for OUR bug!
jp...@google.com <jp...@google.com> #31
fix this bug immediately.
hu...@gmail.com <hu...@gmail.com> #32
Even translated into Chinese, and proposed to 'average' translated into "日均" or "平均".
竟然翻译成中文了,建议把‘average’翻译成“日均”或者“平均”。
竟然翻译成中文了,建议把‘average’翻译成“日均”或者“平均”。
jp...@google.com <jp...@google.com>
ni...@noovle.com <ni...@noovle.com> #33
Please fix this bug
jp...@google.com <jp...@google.com>
[Deleted User] <[Deleted User]> #34
This is just sad... :/
Description
not already been reported.
Please provide a short description of the issue:
When copying an existing Google Sheet with attached Google Script code containing custom functions (accessed as spreadsheet functions) using Google_Service_Drive_Files_Resource->files->copy($fileId, Google_Service_Drive_DriveFile) when the authenticated user is a Google Service Account user, the custom functions are not accessible in the copied Sheet and the following error is returned when they are accessed: "Server error occured. Please try saving the project again. (line 0)."
Please provide a small sample script that reliably reproduces the issue.
The sample should run as-is or with minimal setup, without external
dependencies.
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
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.
MoVtor4Bp7KuXe8BsOnskPbLoayAtuwAq
Please provide any additional information below.
This was working prior to 15 October 2015 and is now causing failures in our production system.
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.