You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installation stops with the message that @abandonware/noble 1.9.2-23 does not support Android.
I do have @abandonware/noble v.1.9.2-23 and v.1.9.2-24 installed. I was able to install those separately by adding 'android' to OS list in package[-lock].json.
However, prior installation of @abandonware/noble v.1.9.2-23, and addition of 'android' to OS list under @abandonware/noble 1.9.2-23 section plus changing repository path to the local one (where I previously succeeded installing @abandonware/noble v.1.9.2-23 from) in package-lock.json of homebridge-homekit-control package, does not help. The installation does not check for nor recognize installed @abandonware/noble v.1.9.2-23 and stops with unsupported OS message.
Please include check for installed @abandonware/noble v.1.9.2-23 and/or somehow disable OS check by @abandonware/noble v.1.9.2-23.
Thank you.
The text was updated successfully, but these errors were encountered:
Installation stops with the message that @abandonware/noble 1.9.2-23 does not support Android.
I do have @abandonware/noble v.1.9.2-23 and v.1.9.2-24 installed. I was able to install those separately by adding 'android' to OS list in package[-lock].json.
However, prior installation of @abandonware/noble v.1.9.2-23, and addition of 'android' to OS list under @abandonware/noble 1.9.2-23 section plus changing repository path to the local one (where I previously succeeded installing @abandonware/noble v.1.9.2-23 from) in package-lock.json of homebridge-homekit-control package, does not help. The installation does not check for nor recognize installed @abandonware/noble v.1.9.2-23 and stops with unsupported OS message.
Please include check for installed @abandonware/noble v.1.9.2-23 and/or somehow disable OS check by @abandonware/noble v.1.9.2-23.
Thank you.
The text was updated successfully, but these errors were encountered: