Search results for:

@mstaatz you should be able to get the bar at the bottom back by tapping at the bottom of the screen (where it should be). That's a feature, not a bug :-)

I haven't tried the Bangle with WebBLE yet, @Gordon do you have any non-ancient iOS devices lying around you could give it a go with?

@user93698 I raise https://github.com/daphtdazz/BleBrowser/issues/8 to track this. For now you can workaround by setting acceptAllDevices to true and filtering in the app.

Hi @user93698, 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.

Hmm, it seems that the web inspector is disabled for apps downloaded from the app store. I'm just investigating whether that's something I can turn on, otherwise you could always build WebBLE yourself and run it in debug mode locally which will allow it to work. Or you can hack console.log() to send it to a <div> on your page or something like that (which is what I used to do).

Coincidentally I just updated the faqs with this very thing!

Could you post here if it works? I'd like to know if my guide was clear enough / works on someone else's device.

WebBLE 1.1.2 has now been accepted by Apple, so if you upgrade you should be able to use acceptAllDevices too.

In the current version (1.1.1) the only filters that should be supported are "services" and "namePrefix". I'll add "name" to 1.1.2, which I'm preparing now.

( @hydronics your published code had a small bug, where you used options instead of options1, but that's just FYI.)

WebBLE says it supports it so I guess it should :-) However, it doesn't seem to work at the moment, and looking at the code it looks like I didn't implement it. Given I said it is supported I think I should make it so! I'll try and get an update submitted to Apple today or tomorrow.

Edit: also this might help @user73018

@user73018: as Gordon says there is no way to enable Safari Remote Debugging in the browser unfortunately. A console window is next on my todo list for the app, but can't say when I might get around to it... sooner if more people ask for it!

"basic bookmark facility"... done :-)

Apple have accepted an enhancement I made over the weekend to add bookmarks support to WebBLE, so it's now easy to save your favourite Web Bluetooth pages and return to them later.

The update should get pushed out to everyone soon.

See the WebBLE announcement conversation for more info on WebBLE on iOS.

Also fixed in this version:

• if you typed just e.g. http://www.greenparksoftware.co.uk into the url location, it would try (and fail) to take you to the insecure http://www.greenparksoftware.co.uk location.
  

It would be nice as well, not as the actual landing page but perhaps linked from it, to have a page which runs a bunch of unittest against the API, so that you can navigate to it from different bluetooth enabled browsers and see whether and to what extent they conform or not. A bit like http://html5test.com or something. Basically I'm trying to avoid doing all that boring testing stuff myself.

Maybe Google has got something already they could share...

Hmm, I get both when I search for webble on the app store from my iPhone, perhaps it just hasn't filtered through all Apple's servers yet..?

I'll talk with Gordon and see if we can work out a better landing page to go to.

Bookmarks is certainly something I'd like to do if I can get some time (and/or if it proves popular).

Freelance developer at greenparksoftware.co.uk

Also, for those links that would open a new window / tab, you can always long hold on them and then hit the Copy Link button to avoid typing it in manually!

It's on my list to fix ;-)