André Kovac

@autofit : My pull-request #6 should solve the sdk issue when running the example. Give it a try.

Good addition! +1 Please merge. Thanks!

@ldn0x7dc Would be great if you update the npm version! I just implemented that change myself again because I also needed `onSingleTapConfirmed` & `onResponderSingleTapConfirmed` in your project [react-native-view-transformer](https://github.com/ldn0x7dc/react-native-view-transformer). You really...

@domoritz @ali-habibzadeh The Issue is still present now. The issue is of general nature: For a property `myProp: number | undefined;` (in an interface/class/type alias) the `undefined` will be swollowed...

@loopingz There's a crucial difference with `undefined`. Facing an issue concerning this difference in my codebase lead me to find the issue here. In fact the case `myParam: string |...

Hi, thanks for the package and for maintaining it! I used your latest version, i.e. commit 72139ade6ea8aee5a5cecc2d452914167e77c8ad with react native 0.22.2.

@joustava : That's exactly the reason why I'm asking the question. Native Android supports BLE from 18 (4.3) onwards, but this package only works for version 21 onwards. Have you...

@joustava Thanks for pointing that out. Currently I'm implementing a bridging module for a different beacon API. I'm not using any transmitting feature but it also only works for Android...

@joustava Thanks! I'll look further into it and give it another try. The weird thing is that it didn't work in my implementation of the other beacon API (Kontakt.io beacons)...

@mmazzarolo Thanks for the info! concerning your question: The kontakt.io SDK offers some additional values like batteryPower, txPower, uniqueID (which is written on the back of the beacons). That's why...