Data-Munching Bug Throws Chrome 79 Android Rollout Into Chaos | Mobile
By Jack M. Germain
Dec 17, 2019 10:32 AM PT
Google has stalled the rollout of its Chrome 79 Web browser for Android units till it may discover a technique to neutralize a data-destroying bug. Affected customers have been vilifying Google and app builders for failing to go off the issue.
The newest Chrome model comprises two extremely anticipated new options: phishing safety, and the power to reorder bookmarks.
Google began rolling out Chrome 79 on Dec. 10, final Wednesday.
App builders and customers started reporting an issue with lacking information in a few of their Android apps by Friday morning, Dec. 13.
As a consequence, Google on Saturday quickly suspended the Chrome 79 rollout to Android units. Google officers stated the rollout had reached 50 p.c of Android customers.
A patch for the issue might be obtainable in 5 to seven days, in response to Google. Until then the rollout is not going to proceed.
The bug wipes information in sure apps that use Android’s built-in WebView, the part that renders Web pages inside apps. Chrome kicks in to load content material when customers log right into a Web web page inside an app, or if the default Android browser lacks its personal inner rendering engine.
“It is rare for Google Chrome to let a bug like this leak through,” stated Thomas Hatch, CTO of
“Google has certainly had bugs in releases, but Chrome and the Chromium platform are tested extensively to prevent these issues,” he instructed LinuxInsider.
The change Google made to the Chrome 79 WebView code that its improvement group believes precipitated the issue occurred in a beta model six weeks in the past. Had the problem been picked up at that time, Google
would have been capable of deal with it earlier than it considerably impacted customers, steered a Google software program engineer in a discussion board publish on Sunday.
Google engineers are pretty sure the lacking information is the results of a change in storage location. However, patching that code to remove the issue remains to be difficult engineers. So far no assure exists that the patch will return the lacking information to the impacted Android apps.
Some Android apps run inside WebView. This contains purposes constructed with Apache Cordova or packaged Web apps like Twitter Lite.
The malfunction seems associated to a change in how Chrome 79 handles the situation the place Web information is saved. When units have been up to date to Chrome 79, Web apps and WebView purposes had some (or all) native information rendered unreachable for viewing. Chrome didn’t delete previous information after the migration. That information should be intact however is inaccessible now.
2 Local Storage Containers on Mobile Devices
Mobile units corresponding to Android telephones and tablets depend on nativeStorage and WebSQL areas to offer storage mechanisms. They permit an internet site or Web app to retailer information on a person’s system inside a person’s Chrome profile listing.
Some Android app builders choose to add person information to devoted database servers. Some web sites nonetheless use nativeStorage or WebSQL domestically, nonetheless. Many cell app builders use nativeStorage and WebSQL saved domestically on cell units.
In apply, many Android apps usually are only a web site loaded contained in the WebView part. This course of capabilities as a lightweight model of Chrome. It is a less complicated, extra compact technique for saving person settings and information domestically than an on-board SQLite database.
The two most blatant options to regaining entry to the “deleted” information is to proceed the migration by shifting the missed recordsdata into their new areas, or to reverse the change by shifting migrated recordsdata to their previous areas, in response to Google. Yet developer feedback on the Chromium Bug Forum don’t totally help both resolution. The commonest opinion is to attend out the issue and hope that Google can resolve all the points is a speedy patch issued this week.
Google Chrome builders usually are not totally assured they will salvage or retrieve the lacking person information left behind within the older nativeStorage and WebSQL recordsdata. On some units the Chrome replace course of truly might need wiped the information. A cleanup app course of might need deleted the information after the replace operation, in response to explanations from Google engineers on tech boards.
In making an attempt to repair the mess, one other downside may consequence from shifting the previous recordsdata to the brand new location. That may overwrite new recordsdata the person created for the reason that replace put in, main once more to information loss.
A Waiting Game
Users whose units have but to be up to date to Chrome 79 is probably not subjected to the bug when the brand new model contains the repair, in response to some software program staff. They advise in opposition to deploying it in the event that they run WebView apps, nonetheless.
The downside with Chrome 79 is that individuals are dropping their information. Google is engaged on options, however there’s not a lot those that have misplaced information can do at this level, in response to technician Steve Foley, CEO of
Bulk Memory Cards.
“The best thing people can do now is wait for a revised Chrome 79. There is not even a list of apps it impacts, so without knowing what data is at risk the best course of action is to avoid using Chrome 79 until the issue has been corrected,” he instructed LinuxInsider.
App builders flooded the Chromium bug Tracker discussion board with diatribes about what some described as a “catastrophe” and a “disaster.” After the rollout, finish customers discovered the affected apps appeared to have skilled a reset after which functioned as a brand new set up with no saved information or log-in credentials intact.
App builders on varied boards decried the snafu for damaging their reputations. They complained that many affected customers deleted their apps. Other devs reported that customers have been posting very detrimental evaluations specializing in their specific app’s unreliability because of the information loss.
Google didn’t reply to our request for an replace on the patch progress.