New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QRCodeReader not decoding:com.google.zxing.NotFoundException #216
Comments
It decodes fine, but if you intend to decode a complex pure image you probably want PURE_BARCODE mode. |
Thank you for your prompt response. |
Found it. |
牛逼,解决我的问题了。 |
我用zxing来解码的时候,普通的二维码能解析,但是中间带LOGO的解码的时候报错com.google.zxing.NotFoundException,虽然不是相同的问题,但是这个解决了我的问题。 |
hints.put(DecodeHintType.PURE_BARCODE, Boolean.TRUE); |
hints.put(DecodeHintType.PURE_BARCODE, Boolean.TRUE);加上这,还是报这错误com.google.zxing.NotFoundException |
me too zxing version 3.3.0 |
试试 : hints.put(DecodeHintType.TRY_HARDER, Boolean.TRUE); in https://github.com/zxing/zxing/blob/master/core/src/main/java/com/google/zxing/DecodeHintType.java
|
Dublin Milton
|
js使用的话,怎么解决这种报错 |
but it didnt work for me ,so any other suggestion? |
I optimized zxing, the success rate is very high, you can test it |
能给点建议和方向吗? |
OK, let me have a look first
…------------------ 原始邮件 ------------------
发件人: "何彪"<notifications@github.com>;
发送时间: 2019年12月4日(星期三) 中午1:28
收件人: "zxing/zxing"<zxing@noreply.github.com>;
抄送: "口含薄荷---心微凉"<1115741577@qq.com>;"Comment"<comment@noreply.github.com>;
主题: 回复:[zxing / zxing] QRCodeReader无法解码:com.google.zxing.NotFoundException(#216)
我优化了zxing,成功率很高,可以对其进行测试
https://www.sojson.com/qr/deqr.html
https://www.sojson.com/qr/zxing.html
能给点建议和方向吗?
—
您收到此评论是因为您发表了评论。
直接回复此电子邮件,在GitHub上查看,或取消订阅。
|
我就是把图片色差一直调整!直到出结果 |
Encounter the same problem, solved with the correct colored QRcode image: white and black works fine, other colors produce exceptions. 之前红色出问题,改成黑白一切正常。 |
|
调色差的代码借我抄抄 |
ZXing 3.1.1-SNAPSHOT
Encoded some UTF-8 text to QRCode.
QRCodeReader fails to decode with com.google.zxing.NotFoundException.
Enclosed is the QRCode in question.
The text was updated successfully, but these errors were encountered: