Status Update
No update yet.
Comments
uc...@google.com
I encountered that issue with my project. I have time-based trigger that appoints next run using time-based trigger.
[Deleted User] <[Deleted User]>
Can we reasonably assume that ES5 will not be removed before this issue is resolved?
@mr...@gmail.com: You probably should star this issue (if you haven't yet) if you are affected by it.
@mr...@gmail.com: You probably should star this issue (if you haven't yet) if you are affected by it.
da...@gmail.com
Not sure if this is exactly the same issue, but triggers under V8 get deleted when created programatically from a straight script. This extract is from a bigger piece of code that others have worked on, I've tweaked it to just run the core functions. Under V8 the triggers end up disabled without reason, whereas under ES5 it all works as designed.
var ml_howFrequent = 3;
function ml_install(){
//Delete any already existing triggers so we don't create excessive triggers
deleteAllTriggers();
if (ml_howFrequent < 1){
throw "[ERROR] \"ml_howFrequent\" must be greater than 0.";
}
else{
ScriptApp.newTrigger("ml_install").timeBased().after(ml_howFrequent * 60 * 1000).create();//Schedule next Execution
ScriptApp.newTrigger("ml_startSync").timeBased().after(1000).create();//Start the sync routine
}
}
function ml_startSync(){
Logger.log("Output this");
}
function deleteAllTriggers(){
var triggers = ScriptApp.getProjectTriggers();
for (var i = 0; i < triggers.length; i++){
if (triggers[i].getHandlerFunction() == "ml_startSync" || triggers[i].getHandlerFunction() == "ml_install"){
ScriptApp.deleteTrigger(triggers[i]);
Logger.log(triggers[i].getHandlerFunction(), " has been deleted");
}
}
}
var ml_howFrequent = 3;
function ml_install(){
//Delete any already existing triggers so we don't create excessive triggers
deleteAllTriggers();
if (ml_howFrequent < 1){
throw "[ERROR] \"ml_howFrequent\" must be greater than 0.";
}
else{
ScriptApp.newTrigger("ml_install").timeBased().after(ml_howFrequent * 60 * 1000).create();//Schedule next Execution
ScriptApp.newTrigger("ml_startSync").timeBased().after(1000).create();//Start the sync routine
}
}
function ml_startSync(){
Logger.log("Output this");
}
function deleteAllTriggers(){
var triggers = ScriptApp.getProjectTriggers();
for (var i = 0; i < triggers.length; i++){
if (triggers[i].getHandlerFunction() == "ml_startSync" || triggers[i].getHandlerFunction() == "ml_install"){
ScriptApp.deleteTrigger(triggers[i]);
Logger.log(triggers[i].getHandlerFunction(), " has been deleted");
}
}
}
uc...@google.com
xa...@google.com
je...@google.com
hu...@google.com
Hi
I also have an issue with trigger.
A script published as a web app and create a time trigger, when a new version of the web app is published with V8 runtime the authorization are lost.
So you have to revert runtime to old one and it goes back to normal way.
Stéphane
I also have an issue with trigger.
A script published as a web app and create a time trigger, when a new version of the web app is published with V8 runtime the authorization are lost.
So you have to revert runtime to old one and it goes back to normal way.
Stéphane
xa...@google.com
Hi
I met the same issue here when I tried to create a time-based trigger inside of the script as answered in this post [1].
I have disabled V8 runtime option which made the script working again.
Is there an ETA for this issue?
[1]https://stackoverflow.com/a/8608327
I met the same issue here when I tried to create a time-based trigger inside of the script as answered in this post [1].
I have disabled V8 runtime option which made the script working again.
Is there an ETA for this issue?
[1]
da...@gmail.com
Me too. I only seriously started scripting after v8 was implemented, I thought I was doing something wrong. My script-created triggers work 1/10 times. 9/10 times they seem to be "born" disabled.
hu...@google.com
I have the same issue with this type of code in V8, apparently it hasn't been fixed yet.
Example, I have a trigger for getOrders that runs every 15 minutes, getOrders contains a timeBased trigger for syncStock. This second function gets disabled for unknown reason each time the initial trigger runs.
function getOrders {
// get orders
// delay execution of function syncStock for 2 minutes
var next = ScriptApp.newTrigger("syncStock").timeBased();
next.after(2 * 60 * 1000).create();
}
function syncStock() {
// sync stock
}
Function syncStock keeps getting disabled for unknown reason, it will not run at all.
Example, I have a trigger for getOrders that runs every 15 minutes, getOrders contains a timeBased trigger for syncStock. This second function gets disabled for unknown reason each time the initial trigger runs.
function getOrders {
// get orders
// delay execution of function syncStock for 2 minutes
var next = ScriptApp.newTrigger("syncStock").timeBased();
next.after(2 * 60 * 1000).create();
}
function syncStock() {
// sync stock
}
Function syncStock keeps getting disabled for unknown reason, it will not run at all.
Description
AI-171.4333198, JRE 1.8.0_152-release-915-b01x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.11.6 unknown, screens 1920x1080
IMPORTANT: Please read
Hi, I'm a developer and I've encountered an error today that wasn't occurring yesterday. The stacktrace showed me this:
Caused by: java.lang.NoSuchFieldError: No field INSTANCE of type Lorg/apache/http/message/BasicHeaderValueFormatter; in class Lorg/apache/http/message/BasicHeaderValueFormatter; or its superclasses (declaration of 'org.apache.http.message.BasicHeaderValueFormatter' appears in /system/framework/org.apache.http.legacy.boot.jar)
at org.apache.http.entity.ContentType.toString(ContentType.java:153)
at org.apache.http.entity.mime.MultipartFormEntity.<init>(MultipartFormEntity.java:56)
at org.apache.http.entity.mime.MultipartEntityBuilder.buildEntity(MultipartEntityBuilder.java:236)
at org.apache.http.entity.mime.MultipartEntityBuilder.build(MultipartEntityBuilder.java:240)
at com.myenterprise.network.HttpsPost.sendPost(HttpsPost.java:299)
Then I read the changelogs of the Android Studio 3.0 beta-6 and saw that the way gradle handles httpclient has changed. I think that my crash has something to do with it, since, like I said, i'm pretty sure that it wasn't happening yesterday. What I'm doing is this : HttpEntity httpEntity = reqEntity.build(); and reqEntity is an object of the MultipartEntityBuilder class(from apache.http.entry.mime.
I hope to be of any help ^^
Good luck