Adrian Edwards

> > because pub.dev wont let me publish my own package > > I don't understand this. Why couldn't you publish you own package??? What I meant by this was:...

> I'd just rather move to a library which is maintained and not in an abandoned state. Based on a brief email exchange as a result of filling out the...

> If you have a fork which is null safe then it should not depend on the FlutterBleLib, since it's the fork of FlutterBleLib itself. Just release it in another...

It seems like this only affects published versions prior to the current nullsafe one since I am successfully able to use all-caps UUID's when importing the lib as a local...

it appears the current dev branch supports it courtesy of #586, just hasn't been released to pub.dev yet

I had some comments on this in #613, but it also seems like there's already forks being published so it seems like the community has already got the perception that...

Do you think it would be helpful to try and get everyone with their own forks to converge on using the same fork? Or at least get everyone in a...

the fork ive been using is https://pub.dev/packages/flutter_ble_lib_ios_15 (mentioned in the other issue that i linked earlier along with a couple alternatives). My only concern with having that act as a...

the warning also links to https://flutter.dev/go/android-project-migration

it appears that there is a fork of this project explicitly for supporting iOS 15 at https://github.com/davejlin/flutter_ble_lib_ios_15