Shahar Hadas

This still happens. Mac OS, node v12 Any idea how to resolve this?

I see the disconnect happening around 30 seconds everytime. During those 30 seconds everything works - no idea what's causing this disconnect. Maybe there's an undocumented "keep alive" somewhere in...

@kenr @mitoconcrete I've created a sample project: https://github.com/WeCanDoIT-Ltd/pc-ble-driver-js-test which shows the exact issue by using the `ble_app_uart` from the `nrf5_sdk` examples. It will connect, subscribe for the TX event -...

Updated my test (https://github.com/WeCanDoIT-Ltd/pc-ble-driver-js-test) to try and follow https://devzone.nordicsemi.com/f/nordic-q-a/57789/connecting-to-device-using-pc-ble-driver-py-causes-disconnect-after-60-seconds But it seems unrelated as changing `NEXT_CONN_PARAMS_UPDATE_DELAY` has no affect on the disconnect timeout

I think I resolved the issue - but it might varies with other projects. In my case, I needed to add handling for the following events and **respond** ```js adapter.on('attMtuRequest',...

There's no issue running this on M1. Please see my relevant workaround for having the `pc-ble-driver-py` on M1 for nrfutil You'll need to adapt it to the build process of...

Resolved the issue by creating a parallel brew-x64 installation

This is how I'm getting the error with `0.66` `@IBOutlet weak var imageSplashBackground: UIImageView!` ``` self.imageSplashBackground.makeAlpha(0).duration(0.2) .completion() { self.imageSplashBackground.isHidden = true } .animate() ```

Instead of having to run undo 3 times (per your example), you have the option of using a migration file per version. You can extend that solution by having the...

Still a thing ... +2 years later. Created a PR #899 which should fix the issue. The relevant fields are: `seedersTimestamps` and `migrationTimestamps` which can be set in the sequelize...