iOS 16 needs restoreStateIdentifier specification and has Error 103 issue

[Aldaniee]

I was working on updating the example project to run iOS 14 by adding the following to Runner/Info.plist

	<key>NSBonjourServices</key>
	<array>
		<string>_dartobservatory._tcp</string>
	</array>
    <key>NSBluetoothAlwaysUsageDescription</key>
    <string>The app uses bluetooth to find, connect and transfer data between different devices</string>
    <key>NSBluetoothPeripheralUsageDescription</key>
    <string>The app uses bluetooth to find, connect and transfer data between different devices</string>
    <key>UIBackgroundModes</key>
    <array>
    <string>bluetooth-central</string>
    </array>

And in ergblemanager.dart I added a restoreStateIdentifier.

  Future<void> init() async {
    await _manager.createClient(restoreStateIdentifier: "example-restore-state-identifier");
  }

Now the error I'm stuck on is the following:

[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: BleError (Error code: 103, ATT error code: null, iOS error code: null, Android error code: null, reason: Reason not provided, internal message: null, device ID: null, service UUID: null, characteristic UUID: null, descriptor UUID: null)

Error 103

[MoralCode]

Thanks for finding these! feel free to submit a PR to make those changes to the Info.plist.

Error 103 seems interesting. id be curious as to if it means bluetoth is literally in a state called "unknown", or if that error means bluetooth doesn't know what state its in or cant find out. Is bluetooth turned on on the device you are testing with?

[Aldaniee]

The issue came from startErgScan() being called before init() in ergblemanager.dart.

The fix I found was to make init() async and in main.dart to call the async functions in a synchronous way:

  @override
  void initState() {
    super.initState();
    unawaited(
      bleManager.init().then((_) => startScan()),
    );
  }

[MoralCode]

your PR for this was merged as part of #26 (although i wouldnt be surprised if more iOS issues have come up due to new iOS versions since then)