I am using Web Bluetooth API to write to a characteristic of a PCB board. I am able to successfully write to the characteristic via Chrome on Windows laptop.
If i try the same code via Chrome on Android 10, I get a DOM Exception: GATT Error Unknown.
I am writing a Uint8Array of length 493. I tried writing the entire data and also in chunks of 10. In both cases, I am getting an error in Mobile device.
Can someone please help?
I am using Chrome browser version 91.
UPDATE:
Added Code Snippet. I am calling a Python API to fetch data to be written to the characteristic and converting the data to Uint8Array. I tried to write the entire data via mobile but it wasn't working. Found this link which says to write data in chunks. So I tried that as well. Still same error.
UPDATE 2: I tried the methods writeValue and writeValueWithoutResponse. I am getting GATT server disconnected error. I tried this link to try to fix the same. But it still persists. I have attached the screenshot for the same.
UPDATE 3:
I tried with adding an event listener. I tried the same code from laptop and mobile device. It works on laptop successfully and gives off error on mobile. I have attached screenshots for both laptop and mobile.
To get help you likely need to reduce the problem to simple code
samples that you can share. Ideally these work with common devices that others can test too.
https://www.chromium.org/developers/how-tos/file-web-bluetooth-bugs includes tips on how to capture logs and test with other devices.
Related
Im using the Capacitor community sqlite plugin and it was working all along. I added a few more pages to my Ionic app and build the app again and this error started. Im getting this error in the Android Studio IDE when i run the app
I was expecting the app would run as usual
CapacitorSQLPlugin: Protocol message contained in invalid tag (zero)
I have the same problem. But it doesn't happen to me on all devices. In virtual machines it seems to work fine (Pixel 3). On an OPPO Android 12 physical phone, the error occurs. On a CAT phone with android 11 it worked fine too.
In case it may be of interest to you, I have sent an incident to capacitor-community.
https://github.com/capacitor-community/sqlite/issues
My app is using Firebase Analytics and I believe starting in iOS 13.2 started getting the errors described here: Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?
I guess it wasn't a big deal
Since I planned for my app to go live in January, I began bigger tests in physical devices. I noticed after a while the app started to behave erratically, specially after receiving a [general] Connection to daemon was invalidated error. This doesn't occur in the simulator
Searching the internet I found a post that describes the same problem: https://forums.developer.apple.com/thread/124306
In my case, only Firebase seems to be calling WKWebView, but every time I open the UIMenuController I get the error described in the console and the app appears to be missing inputs. This is specially troublesome with UIScrollViews, which my app uses a lot. The pinch gesture seems to work at will. On an iPhone 6s, the issue isn't as noticeable, on an iPad, it's like a 50% chance the pinch gesture will work properly
Outside of removing Firebase, is there a way to mitigate this issue?
1 June 2020: The console message still persists, however, I have seemed to resolve the UIScrollView issue by deactivating delaysContentTouches, now the pinch gesture seems to work most of the time
23 October 2020 If anyone notices their app starting to behave erratically with no apparent reason I HIGHLY suggest to test it on an iOS 13 physical device if possible. Seems that Apple removed the warning from iOS 14, but testing it on iOS 13 you can pin point the exact reason after the warning appears in the console
Upon further testing, I've reduced the view down to a dead-simple UI view with a single SwiftUI TextField and the 'Connection to daemon was invalidated' still appears after I type the first character into the field. Soon thereafter the app crashes with a sigAbort. (So I don't think the reason is the UITextView wrapper I was using in the previous post). Once the invalidated message appears the app is doomed to crash, not right away but soon thereafter.
I have no idea what causes the 'invalidate' message and a Google search seems to imply that no-one else does either. Some folks appear to have made (experimental?) changes to their UI that stops the message but it appears to be impossible to determine a definite cause. (and like before it only occurs on a real phone)
Same issue without using Firebase at all. What I did: Delete build folder and compile again. Issue does not appears again.
On Xcode:
Clean the Build Folder
This will delete all of the products and intermediate files in the build folder. To clean the build folder you can use the shortcut Command+Option+Shift+K or Menu Bar → Product → Hold Option Key → Clean build Folder.
On Flutter:
Just delete build folder.
I've read similar questions others have had in using FTDI (CDC Class) and WebUSB, however none of the suggested answers have worked for me.
I'm trying to communicate to an Arudino Mega via:
this.device_.selectConfiguration(1)
this.device_.claimInterface(0); // or this.device_.claimInterface(1);
but I get a DOMException.. and chrome://device-log shows the device in blue ("USB user").
I know Chrome must use an interface that is not bound or attached to Windows, however, the USBconfiguration shows 2 interfaces, both not claimed, and yet I can't claim either.
Despite trying to uninstall and use WinUsb.sys, Windows always loads the ftdiport.sys driver NOT WinUsb.sys. Not sure what could be the problem.
The two interfaces are listed as unclaimed because your page hasn't claimed them. Whether or not there is another application or driver on the system claiming the interface is not reflected in the API.
Fighting with Windows to not load ftdiport.sys may be a losing battle. I am working on implementing the Serial API in Chrome which should offer a better solution for this class of devices. Alternatively, have you tried installing the WinUSB driver with the Zadig tool?
i installed bluestacks on my windows 10 laptop (HP elitebook ) , it worked well the first time , i installed whatsapp on it ,it worked properly for few minitues messages started flowing but i couldnt get the chance to read them because my laptop frozes for seconds so i restarded it, the next time i started bluestacks after opening the laptop i found that it went back to initializing phase, i'm forever stuck there.
i'm not sure if it needs a good internet to initialize
for the second time?
if not , why it stucks in initializing , i tried multiple suggestions i found on internet (like compatibility solution) but didnt work out.
if there is nothing to do, how can i extract whatsapp database so i can read my chats on another device.
if i installed whatsapp on another device, i won't get the messages i recieved once on bluestack again,right?
please help me whatsapp chats are so important to me.
you can't able to restore those chats again
if you are using windows 10 directly download whats app to your lap directly from store or go to link https://www.whatsapp.com/download/
When I open my Firebase hosted site (built with Polymer Starter Kit) using my computer that I deployed (i.e., using $ firebase deploy) the app from, it works great. It works on all browsers too.
However, when I try to open it on my mobile device (an Android tablet in this case) I get a Site Not Found Error. The full error text message reads as follows:
Site Not Found
Why am I seeing this?
There are a few potential reasons:
You haven't deployed an app yet.
You may have deployed an empty directory.
This is a custom domain but we haven't finished setting it up yet.
How can I deploy my first app?
Refer to our hosting documentation to get started.
Obviously, none of the possible causes listed are actually the case because, as mentioned, the site tests fine on my deploying device. And on all browsers on that device.
Question
What could be causing this?
TL;DR: User error. Problem fixed.
I just tested it again and it worked on the other devices. Since I was not clicking a link, but rather, typing it instead, I think that was what caused the problem.
I think what happened was the "en dash" character on some soft keypads looks like a different character (maybe em dash?) which causes the typed URL not to match the actual URL if the user is not used to typing out URLs and doesn't know how to tell the difference on a soft keypad between the different types of dashes.