-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Must be handling a user gesture to show a permission request #24
Comments
You need to place the call in a button. It's a security thing in the web browser API. |
I did, this only works once.
or
Checked all Ids with edge://bluetooth-internals/#devices, and they are correct. When I "forget" the device I am able to pair again. |
This is the error message in the output window
|
I fixed some problems by updating the firmware of my device. Most of the functionality works now. Only exception left is that I get when attaching the notification handler: 'GATT Error: Not supported.\nundefined' Could this be related to the device? |
It could be. I have noticed this kind of problem before, but I don't think (I'm really guessing here) it is related to the Blazor implementation. It might be the browser implementation, or it might be the device. |
I added the NuGet package to my Blazor WASM App and get following error message:
_message 'Failed to execute 'requestDevice' on 'Bluetooth': Must be handling a user gesture to show a permission request.\n Error: Failed to execute 'requestDevice' on 'Bluetooth': Must be handling a user gesture to show a permission request.\n at Module.requestDevice (https://localhost:44398/_content/Blazm.Bluetooth/Blazm.Bluetooth.js:7:44)\n at https://localhost:44398/_framework/blazor.webassembly.js:1:3332\n at new Promise (<anonymous>)\n at Object.beginInvokeJSFromDotNet (https://localhost:4439…(https://localhost:44398/_framework/blazor.webassembly.js:1:59849)\n at _mono_wasm_invoke_js_blazor (https://localhost:44398/_framework/dotnet.6.0.18.gsaaqh5ry8.js:1:195300)\n at https://localhost:44398/_framework/dotnet.wasm:wasm-function[219]:0x1a4c1\n at https://localhost:44398/_framework/dotnet.wasm:wasm-function[167]:0xce8f\n at https://localhost:44398/_framework/dotnet.wasm:wasm-function[166]:0xbd73\n at https://localhost:44398/_framework/dotnet.wasm:wasm-function[2815]:0xabf2c' string
The text was updated successfully, but these errors were encountered: