Google Chrome 79 started turning out on work area and portable stages a week ago, and a bug in the discharge was later found that caused data put away by web applications (just as local applications utilizing a WebView compartment) to evaporate. Following a couple of long periods of investigating, the Chrome group is currently revealing a fix.
The bug originates from a straightforward change made in Chrome 79, where the area where web data is put away was refreshed. As one remark on a Chromium bug page brought up, data from localStorage and WebSQL — two kinds of capacity generally utilized by web applications and bundled applications — wasn't moved appropriately. At the point when gadgets were refreshed to Chrome 79, a few (or every) neighborhood datum for applications depending on those capacity techniques disappeared.
Google says that Chrome 79 just turned out to 15% of gadgets by the bug was found, not half, as was recently detailed. The organization gave us the accompanying statement:
"The M79 update to Chrome and WebView on Android devices was suspended after detecting an issue in WebView where some users’ app data was not visible within those apps. This app data was not lost and will be made visible in apps when we deliver an update this week. We apologize for any inconvenience."
A bug page remark clarifies a portion of the specialized subtleties — the most recent update appropriately relocates the capacity, and if new data has been made in the new stockpiling area (e.g., if the client previously refreshed to the messed up Chrome 79 form), the new data will be overwritten with the pre-79 stockpiling. data made while the messed up Chrome 79 update was introduced will stay available in a different area, so web applications can recuperate that data if completely essential.
Along these lines, long story short, any data you may have lost after the Chrome 79 update should return to you quickly.
No comments:
Post a Comment