本文介绍了使用Chrome版本50.0.2661.75破解Ripple - “aw snapp”错误信息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Apache-Ripple工作正常,直到Chrome更新到版本50.0.2661.75米。



我使用纹波而不是铬扩展,但正如本文中所解释的:



如果我尝试使用空的Cordova项目,则会收到aw snap消息。在开发控制台中,我可以看到XHR和Fetch出错了用户代理(状态码500)和config.xml(状态码404)。如果我在IE(MS Edge 25.10586.0.0)中运行相同的Cordova / Ripple项目,我也会得到这些消息:因此它失败,但这是正常的,因为在IE Ripple工程中(但因为我需要WebSQL IE是不够的)。



我在Chrome中刷新了所有缓存信息并重新启动计算机,但没有帮助。

如果有人找到解决办法,我会很感激,知道如何。或者-if Ripple太过弃用,无法在Chrome的更新中生存 - 让我知道更新的工具来测试Cordova混合应用的建议。

我已经向chrome报告了错误,他们给了我反馈,表示它已经修复,并将在51版本中提供。



同时,下面是我发现的解决方法运行Ripple / Cordova:

我已经安装了Opera(版本号36.0.2130.66)。 Opera的功能是WebSQL,这是我需要的重要功能。

Apache-Ripple was working correctly until chrome updated to version 50.0.2661.75 m.

I use ripple not as a chrome-extension but as explained in this article:https://www.raymondcamden.com/2013/11/05/Ripple-is-Reborn/

If I try with an empty Cordova project, I get the "aw snap" message. In the development console I can see that "XHR and Fetch" are going wrong for "user-agent" (status code 500) and "config.xml" (status code 404). I do get those messages as well if I run same Cordova/Ripple project in IE (MS Edge 25.10586.0.0): So it fails but it is normal, because in IE Ripple works (but since I need WebSQL IE is not enough).

I did a flush of all cache info in Chrome and computer restart... It did not help.

If anyone find a way around, I'd be grateful to know how. Or -if Ripple is too deprecated to survive Chrome's updates- let me know suggestions of newer tools to test Cordova hybrid app.

解决方案

I ve reported the error to chrome, they gave me the feedback that it was fixed and will be available in the version 51.

Meanwhile, here is the workaround I found to run Ripple/Cordova:

I've installed Opera (version 36.0.2130.66). Opera does feature WebSQL which was the important thing I needed.

这篇关于使用Chrome版本50.0.2661.75破解Ripple - “aw snapp”错误信息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-21 19:47