Same for me (Mojave 10.14, MacBook Pro (Retina, 15-inch, Mid 2015))

figured out. some xpc events changed. hope author will fix this, or ill suggest a PR

There's an open PR here: #804
More testing and code review on that would be appreciated.

Happened the same for me too, don't see the peripherals after the Mojave update.

Same here. Does not found anything at all. Mojave 10.14 + Xcode 10.0.

Same here.Does not found anything

@moki298 @webartistse @akinyema take a look at the PR I mentioned and test, please.

@monteslu Hi, i don't really understand how to test it, which file do i need to put that code/change? Thanks

@monteslu I've tried using Timeular/noble-mac, but it is still not discovering the peripheral that I am trying to connect to. It does discover other peripherals but not the one I need.

@monteslu I've tried using Timeular/noble-mac, but it is still not discovering the peripheral that I am trying to connect to. It does discover other peripherals but not the one I need.

did they connectable? check ur configs. noblemac used patch fixes that working. or just to dig deeper (enable debug npm pack for noble and check what devices it discover. possibly it can be device issue that not broadcasting required info/perms)

@monteslu Is it possible that it's not discoverable with noble-mac even though it was discoverable with noble before MacOS Mojave? What should I check for as far as broadcasting goes? I can see my peripheral through the Light Blue Explorer app on my iPhone 7.

Is it possible that it's not discoverable with noble-mac even though it was discoverable with noble before MacOS Mojave? What should I check for as far as broadcasting goes? I can see my peripheral through the Light Blue Explorer app on my iPhone 7.

if u want, u can get patch changes and use it by own in node_modules, adding some files / replacing some code.

also try to clean node_modules and npm cache. coz changes for Mojave only in pointers. so i can bet dat caches issue

also, u can directly checkout the commit, setting url in package.json file

@monteslu I installed noble-mac and it worked as expected.

@monteslu gonna run some tests on project tomorrow evening, but in common seems legit

@webartistse What device are you connecting to? I've cleaned the cache and re-installed all modules, but the peripheral still isn't being found. It may be an issue with the device, but if so, then noble-mac is no longer compatible with a subset of devices that worked fine with noble.

I have it in my package.json file as a dependency. This is what I have:
"noble-mac": "git://github.com/Timeular/noble-mac.git"

@jaret32 what kind of device u trying to connect? and rly try to checkout exact commit mentioned above (for noble)

@tagrim https://learn.adafruit.com/adafruit-feather-32u4-bluefruit-le/overview

@jaret32 I havn't done more than finding peripherals atm. With noble I didn't find a single one, after installed noble-mac I can find around 30 devices.

Yes, I find devices as well now, just not the one I need haha.

@jaret32 I may have the same problem then. Because I tried to find some ibeacons. I didn't find them right away. I will try to change the batteries because they don't have any led to show if they are on or off.

Okay, let me know. Thanks!

This seems to work so far Timeular/noble-mac#7

Same issue, this worked for me.

Hi guys,
Since i updated and i stated using noble-mac all the bluetooth devices around me get connected to even though i specified which device to connect to. I would appreciate if someone could tell me how to solve this problem

@akinyema Where can I import noble-mac from? Should I install npm package?

@zach-luman I installed noble-mac from here and it's working really well for me!

@charliegerard you might like to use the @abandonware/noble account then as it's started being maintained more over there 🙂

I used Mojave 10.14.6, running the code found in the sample documentation, and still have no output, so this problem has not been solved yet?

I'm also wondering about compatibility with recent versions of macOS. I'm on 10.15

Relate-to: #923 (comment)