Issue with QR code in the desktop app

[VDAODAO]

Hi !

Whereas I have no issues when I try to "add via QR code" in the in-browser app, I can't get it to work in the desktop app. It gives me the following error : "Uncaught error. Something went wrong with the query and rendering of this component. Failed to construct 'Worker': Access to the script at 'blob:file:///a61f0d6d-b238-40b5-a1f3-15e899dd8af3' is denied by the document's Content Security Policy."

I’m on macOS Catalina 10.15.7, version of the app is 0.81.1. I also tried it on another macOS computer, same issue.

Any idea on what to do ?

Thanks for the great work here !

[jacogr]

Weird. Sadly no workaround for this type of issue. This is definitely an overly-restrictive config somewhere in the desktop security that disallows it.

Will see how and why it does it.

Earliest release with a solution I can promise is next week Monday as part of the next release cycle for the desktop client - which is not great, hence just setting expectations up-front.

[VDAODAO]

Thanks a lot for looking at it !

[jacogr]

No crashes as of 0.83.1... but the Electron app cannot get the camera permissions, at least not for me on Mac OS. So still broken in my case.

More work required - https://www.electronjs.org/docs/api/system-preferences#systempreferencesaskformediaaccessmediatype-macos

[kianenigma]

Confirming the same. Not possible to get camera access on Mac

[heisler98]

I'm leaving this bit of info here:

I can get the camera scan to work if I route app launch through a shell...e.g. run /Applications/Polkadot-JS\ Apps.app/Contents/MacOS/Polkadot-JS\ Apps in iTerm. When I add an account via QR, macOS will ask me if I want to let iTerm access the camera.

Usually this happens when the host app isn't properly asking macOS for camera permission, which is a common problem. Apple has extensive documentation on how to properly request auth for media capture, if it's of any use when using Electron.

[wachulski]

Here are my quick findings:
The app uses @polkadot/react-qr which in turns employs react-qr-reader by JodusNodus author, who states the following:
https://github.com/JodusNodus/react-qr-reader#known-issues

Server side rendering won't work so only require the component when rendering in a browser environment.
Due to browser implementations the camera can only be accessed over https or localhost.
In Firefox a prompt will be shown to the user asking which camera to use, so facingMode will not affect it.
On IOS 11 it is only supported on Safari and not on Chrome or Firefox due to Apple making the API not available to 3rd party browsers.

There is a similar issue in there:
JodusNodus/react-qr-reader#36 (comment) which states:

The module uses many things that are browser specific. I'm not familiar with next.js but you should be able to avoid rendering it server side.

My conclusion:
Not supported unless we replace the reader facility in @polkadot/react-qr

[wachulski]

When I debug the electron app with https://github.com/bytedance/debugtron then it works as in the browser (macOS prompts me if I want to allow Debugron access my video camera, I agree and it works then).

[jacogr]

Have we tried this - https://www.electronjs.org/docs/api/system-preferences#systempreferencesaskformediaaccessmediatype-macos to get the same effect? (Not sure how that translates to other environments...)

[wachulski]

ah, I got your point now @jacogr: attempting to ask for permissions upfront so then the QR reading library won't hit any obstacle.

[jacogr]

No idea, just spitballing. But basically since it really doesn't seem to be a file issue (you got it to work), it is permissions only. Either way, we don't ask for it, so really should...

[wachulski]

Good news! Mere addition of NSCameraUsageDescription via electron-builder.yml to Info.plist helped. At least it seems so. Will test a bit more and create a PR.

[jacogr]

Closed in #5569 - will be in Monday's release.

[wachulski]

I doesn't work in 93.1 either. Looking into it now. I suspect macOS detects its origin as github.com download and rejects the app asking for permission.

[wachulski]

Comparing the contents of Info.plist files (locally built which works and release download which does not) gives no diff except:

1. version

<key>CFBundleShortVersionString</key>
<string>0.93.1</string>
<key>CFBundleVersion</key>
<string>0.93.1</string>

2. integrity

<key>AsarIntegrity</key>
<string>{&#34;checksums&#34;:{&#34;app.asar&#34;:&#34;SRplUtvkiTlCFYgN3o9WtRJ1G6BYV14VBPKQn17be/iMCAzFjknbffeN27cJrZnYwMiGfangTtVl+1tqjGxk9Q==&#34;}}</string>
    

which is as expected and does not explain the behaviour difference

[wachulski]

Also: the downloaded release DMG has the following attributes:

com.apple.diskimages.fsck
com.apple.diskimages.recentcksum
com.apple.macl
com.apple.metadata:kMDItemWhereFroms
com.apple.quarantine

When I remove all, it still does not help - the released app does not ask to use the camera permission whereas the locally built release package does.

[wachulski]

I'm running out of ideas.

When I debug the app in Debugtron, it works as it is Debugstron who asks for camera permission.

[jacogr]

Believe we need this as well - <key>com.apple.security.device.camera</key>

So if we add that, I guess let's add a CHANGELOG entry for the version and drop the check in workflow - that way we can get an intermediate build via CI to check since weirdly, local and CI don't match.

[wachulski]

I could bet all my dev-network tokens it won't help, but let's try it out :D

[jacogr]

The above keep on popping up in comments that is linked from electron on the same "Mac doesn't ask for permission" issues... Really clueless, since locally should be the same as CI. Which makes things a huge PITA.

[jacogr]

Verified as working on my machine in 0.97.1 (so #5604 seems to have been the fix indeed)

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.