一直显示无法扫描到有效的二维码 #1250
Comments
|
我也是啊 一直扫不了二维码是怎么回事 说无效二维码 |
|
我的也是，手机上分享出来的二维码，电脑扫不了 |
|
确定你的二维码窗口在前面?
这样是不算的. |
hiddenSharp429
added a commit
to hiddenSharp429/ShadowsocksX-NG
that referenced
this issue
Oct 28, 2024
…owsocks#1250 Improve the clarity of notifications in the QR code scanning feature: 1. Permission handling: - Show notification when screen recording permission is missing - Automatically open system settings for permission grant 2. Enhanced scanning status notifications: When no QR code found: - Title: "Scanned X displays" - Subtitle: "No QR codes found" - Body: "Try adjusting the QR code position on your screen" When invalid QR codes found: - Title: "Found X QR code(s)" - Subtitle: "No valid Shadowsocks URLs" - Body: "QR codes found are not Shadowsocks configuration" When valid QR codes found: - Title: "Found X Shadowsocks URL(s)" - Subtitle: "Scanned X displays, found X QR codes" - Body: "Successfully added X server configuration(s)"
lkebin
added a commit
that referenced
this issue
Oct 29, 2024
Feat(QRCode): Enhance 'Scan QR Code From Screen' notifications # #1250
|
可能是没有开启录制权限的原因，也有可能是二维码确实是无效的，我在新版本上完善了扫描屏幕上二维码的功能，可以在新版本上试试看 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
我一直在使用shadowsocksX-NG 1.9.2版本，但是突然没有办法从屏幕上面扫描到有效的二维码添加节点（我将macOS升级到了Catalina系统后发现），我之后升级到了1.9.4的版本，但是还是有同样的问题。
To Reproduce
Steps to reproduce the behavior
Expected behavior
希望可以成功扫描二维码添加节点
Screenshots
If applicable, add screenshots to help explain your problem.
System and Shadowsocksx-NG version: (please complete the following information):
Diagnoisis file:
ShadowsocksX-NG_diagnose_20200203_112335.txt
ss-local.log
Please upload the ss-local.log file here the file is in
~/Library/Logsss-local的副本.log
Application log
Open the
Console.appand searchShadowsocksx-NGCopy paste the log here
Crash Log
If the app crashes and pop up a crash log, please copy and paste here
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: