please help me on my question.
I want to log it every 10 days on chrome kiosk mode.
But, overwrite user/.config/google-chrome/chrome_debug.log when chrome is turned on.
I want to leave the log at intervals of 10 days and check the logs up to 10 days ago when a problem occurs.
Help me,,, please
Related
When I was developing my Chrome extension I used the alarms API, and it worked without any issues. After uploading it to the Chrome Web Store, it doesn't trigger at the scheduled times (I am settings timers greater than one minute). I tested with a 5 minute timer, and it took 5 minutes and 47 seconds to trigger. I am considering switching to setting a timeout for the timers, but would prefer to use the alarms API. Below is a screenshot of the scheduled time going over the actual time.
Any ideas on how to fix this?
How much time will it take for Google to finish its review for a extension before it gets published to the Chrome Web Store?
Review times vary; some reviews complete in a few hours, others take many days, and in some cases a review can take several weeks
https://developer.chrome.com/webstore/faq#faq-listing-108
Long time no review, many days, few weeks. Our users can't wait. This is reason why we moved almost feature of extension from Chrome Extension to our own app
So it's weird. The review now take 10 days because they review all versions like its new. So if you make a push and have a small fix it's another 10 days. And sometimes it is more than 10 days.
This means a different strategy towards trying to get your extension deployed. First we are setting up a testing item in the Chrome Store Dev Section so that we can test our extension extensively in Chrome.
Second we are looking at using eval() in order to put our code in a wrapper. We already do this for FF and Safari. The real goal is to move more and more of the processing to the back end so that the need for a deployment becomes rarer.
This sounds like a lot of hoops but if you look at it from Chrome's end and the issues they have had around people doing bad things with extensions this is the price that has to be paid in order to be able to make extensions from their point of view.
I published a chrome extension and you can access it only by clicking the link to chrome web store from chrome developer dashboard, but when you search it on the store you can't find it.
I had the same problem. You need to wait around an hour for it to register. Judging by the timestamp of the question, you should be able to see it now. For most people it will take an hour, but some users have reported that it took about a day.
I saw a similar answer here Parsed date has minute difference but it's not exactly the same
I have a problem with google chrome. I have an application developed with GWT. This application sent an RPC to a server, and it get some data in return.
In this data there are some Date object. Seeing this date in EDGE and Firefox everything is ok but in Chrome they have 11 minute less.
I don't think it's a "code parsing" problem... because if I watch the RPC answer in Firefox and Chrome, I can see the RPC answer already wrong.
In firefox I see the object as "jsdate: Date 1800-01-01-01T07:30:00.000Z" and this is what I expect
In chrome I see the object as "jsdate: 1800 08:19:56 GMT+0049"
you can see image of devtool screenshot with the link below
firefox
chrome
In chrome version 69 i get this
In older version of chrome (for example 63) i get the same as firefox
Note that the time in Italy in 1800 was a bit different than now -
https://www.timeanddate.com/time/zone/italy/rome (pick 1800 - 1849 in "Time zone changes for:")
https://www.timeanddate.com/time/zone/italy
In Italy, standard time was introduced in 1893. Until then, the
country had been using solar mean time, based on Italy's longitude. It
was 49 minutes and 56 seconds ahead of GMT, then the world's time
standard.
In 1893, Italy advanced its clocks by 10 minutes and 4 seconds, so the
local time was exactly 1 hour ahead of GMT. The country still uses
this local time as standard time today.
So I am not sure this is a bug in Chrome, but a feature. I think Chrome simply updated their time zone data to include data for older times and it is now more accurate. Other browsers may follow suite at some point.
Since new Date(...) converts the input to the local time, the time zone is taken into account.
I have a Google Spreadsheet addon that has been running for a while now.
A few days ago, due to to a change that happened on my company's server side, I submitted a new version to be published. Usually, this takes about 30 minutes. However, this time I got a notice that my update should be reviewed.
I've got 2 issues:
1. It has been days, and the item is still pending review
2. Another back-end change caused my first fix to be insufficient; however, I cannot push a newer version while the current is under review.
My addon is currently not functional, so I'm hoping to get a quick resolution.
How can I unsubmit the existing published version?
You can fill this form, so your issue can be attended by Google: https://support.google.com/chrome_webstore/contact/developer_support/?hl=en