-
-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
二维码扫描无法工作 #1314
Comments
广告哪里来的很多了?就 1 个而已 |
二维码确实扫描有问题 |
@pexcn 首先,我想说的是,我是希望这个项目朝着一个好的方向发展的。关于广告的问题,抱歉本人在FAQ中实在没有找到答案,然而在早先的issue中我可以大概知道是因为创收的问题,所以对广告的存在表示能够理解(issue已经修改)。如果有机会的话,还是希望能够提供有着内购渠道或者捐赠的版本。之后的话,二维码扫描的确是不能用的,很多人也证实了这个issue的reproducibility,所以我认为这不是一个个例。最后,希望能有一个正反馈吧。 |
@Great-Li-Xin 你用什么文本生成的二维码?举个例子? |
@pexcn 直接使用ShadowsocksX-NG生成的服务器信息二维码 |
@Great-Li-Xin 二维码的文本形式是? |
Please follow #1308 (comment) to post your QR code here. You can generate a QR code with https://shadowsocks.org/en/config/quick-guide.html |
{
"configs":[
{
"remarks":"testService",
"server":"test.service.com",
"server_port":"65535",
"password":"testService",
"method":"rc4-md5",
"obfs":"plain",
"obfsparam":"",
"remarks_base64":"576O5Zu957q/6LevMw==",
"group":"",
"tcp_over_udp":false,
"udp_over_tcp":false,
"protocol":"origin",
"obfs_udp":false,
"enable":true
},
],
"index":"0",
"random":false,
"global":false,
"enabled":false,
"shareOverLan":false,
"isDefault":false,
"localPort":"1080",
"pacUrl":null,
"useOnlinePac":false,
"reconnectTimes":"0",
"randomAlgorithm":"0",
"TTL":"0",
"proxyEnable":false,
"proxyType":"0",
"proxyHost":null,
"proxyPort":"0",
"proxyAuthUser":null,
"proxyAuthPass":null,
"authUser":null,
"authPass":null,
"autoban":false
} @pexcn @madeye 直接从ShadowsocksX-NG手动生成的二维码间歇性可用,这是一个在我这里不可用的案例。对上一个错误案例表示抱歉。 |
已测试,无法重视。 |
你的二维码 decode 出来的格式是:
现在应该是用 https://shadowsocks.org/en/spec/SIP002-URI-Scheme.html 这种格式。 |
The generated QR code follow neither old version nor SIP002.
Please ask the maintainer to remove |
Please read FAQ then answer these questions before submitting your issue. Thanks!
Environment
Configuration
What did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: