search

unicloudvn / esp_provisioning

Flutter Provisioning library for ESP-IDF ESP32 Unified provisioning
https://unicloudgroup.dev
Apache License 2.0
65 stars 52 forks source link

Incompatibility with mqtt_client #19

Open neillowden opened 2 years ago

neillowden commented 2 years ago

I am hitting the following incompatibility when trying to use esp_provisioning and mqtt_client in the same app.

Because mqtt_client >=9.1.0 depends on crypto ^3.0.1 and cryptography >=0.2.6 <2.0.0-nullsafety.0 depends on crypto ^2.0.0, mqtt_client >=9.1.0 is incompatible with cryptography >=0.2.6 <2.0.0-nullsafety.0.
Because esp_provisioning <=1.0.0+5 depends on cryptography ^0.2.6 and esp_provisioning >=1.0.0+6 depends on cryptography ^1.4.1, every version of esp_provisioning requires cryptography ^0.2.6 or ^1.4.1.
Thus, mqtt_client >=9.1.0 is incompatible with esp_provisioning.
So, because flutter_mqtt depends on both mqtt_client ^9.6.1 and esp_provisioning any, version solving failed.

Any suggestions on how to fix or workaround this?

mahmoodfathy commented 2 years ago

@neillowden I have the same issue , have you found any resolution to this ?

neillowden commented 2 years ago

@neillowden I have the same issue , have you found any resolution to this ?

@mahmoodfathy Not yet. I tried building esp_provisioning with newer versions of crypto/ cryptography and Flutter but then got a multitude of null-safety problems. I'm starting to think this package is not actively maintained so I will be looking for alternatives.

mahmoodfathy commented 2 years ago

@neillowden i have resolved this issue momentarily by overriding the crypto dependency by adding in the pubspec.yaml

dependency_overrides:
  crypto: ^2.0.0

but this is just a workaround and i agree with you that this is not actively maintained and we should look for alternatives or make it so we can resolve the null issues and open a PR

zzdota commented 2 years ago

@neillowden i have resolved this issue momentarily by overriding the crypto dependency by adding in the pubspec.yaml

dependency_overrides:
  crypto: ^2.0.0

but this is just a workaround and i agree with you that this is not actively maintained and we should look for alternatives or make it so we can resolve the null issues and open a PR

can not work in my project,issue as follow Because owon_pct513 depends on dependency_overrides from unknown source "crypto", version solving failed. pub get failed (1; Because owon_pct513 depends on dependency_overrides from unknown source "crypto", version solving failed.)