Freelance developer at greenparksoftware.co.uk
Most recent activity
optionalServices is not supported by WebBLE yet, but it should support
namePrefix, but there seems to be a bug in the code meaning it's not working... I'm planning to make a release in a couple of weeks so will put the fix in with that, and might be able to implement
optionalServices at the same time.
From a quick look it seems that it’s something to do with the redirect; if you just go straight to https://s3.us-east-2.amazonaws.com/smarteggdrop.omsi.edu/index.html it seems to work fine. I’ll see if there’s some configuration option I can tweak when I have some time. You may be able to fix it by tweaking the SSL settings you’re using too.
Application cache is being deprecated, right? So I assume you mean service workers.
I’m afraid I don’t know any better than you! Basically WebBLE will support it when it’s rolled out by Apple on mobile Safari and applications that use WebKit. Looks like they’re on it though.
Sorry I can’t help more!
OK, so if I understand straight:
- Customer buys BLE tag or some other small device, say a keyring fob
- Customer downloads your app, or uses your webpage, then hits the "register device" button and registers their BLE device with your service.
- (your service maintains a database of UUIDs of bluetooth devices associated with customers)
- Customer enters store with their BLE device
- POS automatically detects it and loads up their details.
Are you making your own BLE devices? If so, then a way around the randomization of the UUID would be to expose your own GATT service on the device which exposes a persistent ID, and use that instead of the UUID. Then you could easily use WebBLE to do the registration with no further modification (this is what is suggested in the spec).
Good! Sorry it took me a while to get to it :-S
WebBLE on iOS does not pass true device IDs up to the web page, and instead passes random UUIDs to the web page. @Isaac.s is there a particular section of the bluetooth spec that you want implemented that we haven't already? If it's in the spec, then I'd be open to implementing it in WebBLE.
Hey @hydronics, sorry I've been a bit quiet, just started a new job. I'll try and have a look at your problem over the next couple of days, will let you know how I get on.
The more I look into it the more it seems it is not possible to attach the Web Inspector to apps distributed via the App Store :-( See for example this ADC thread.
So for now you can try one of the two options I gave above, or debugging in Chrome on a WebBluetooth enabled PC / Mac first. I would like to add a console page to WebBLE so at least that is visible... but it will depend on whether I can find the time.