Closed TARS-bot closed 6 years ago
I think I have seen this error when trying to use the bitpay api with a tor-proxied electrum.
as a side note: workaround is to use bitpay.com/invoice-noscript
instead of the default bitpay.com/invoice
and manually create the transaction
Are we sure it's not user error?
Copying bitcoin:?r=https/bitpay.com/i/HN4NPuM6VpcxwyxCDKEWsc
into the Pay to
field reproduces this.
sorry, I was mis-remembering. This seems to be a different problem than the tor issue I mentioned above. You are probably right on point.
@bauerj What are the other exceptions from the other reports? Are all of them this "unknown scheme" thing? How do the URLs look like?
Yes:
('unknown scheme', 'https/bitpay.com/i/HN4NPuM6VpcxwyxCDKEWsc')
('unknown scheme', 'https/bitpay.com/i/HN4NPuM6VpcxwyxCDKEWsc')
('unknown scheme', 'opskins.com')
('unknown scheme', 'h')
('unknown scheme', 'h')
('unknown scheme', 'h')
Crash Report
This crash report was reported through the automatic crash reporting system 🤖
Traceback
Reporter
This issue was reported by 8 user(s):
Additional Information