Iced: Iced 0.2 Migration

[janosimas]

I saw the new release and I wanted to upgrade to the new version
but I started getting a weird panic:

thread 'thread 'tokio-runtime-worker[2020-12-13][14:35:01][reqwest::connect][DEBUG] starting new connection: https://translation.googleapis.com/
tokio-runtime-worker' panicked at '' panicked at '[2020-12-13][14:35:01][reqwest::connect][DEBUG] starting new connection: https://pixabay.com/
thread 'not currently running on the Tokio runtime.not currently running on the Tokio runtime.tokio-runtime-worker', [2020-12-13][14:35:01][reqwest::connect][DEBUG] starting new connection: https://translation.googleapis.com/
thread 'C:\Users\janos\.cargo\registry\src\github.com-1285ae84e5963aae\tokio-0.2.23\src\runtime\handle.rstokio-runtime-worker:' panicked at '118thread ':not currently running on the Tokio runtime.', 
' panicked at '[2020-12-13][14:35:01][reqwest::connect][DEBUG] starting new connection: https://translation.googleapis.com/
tokio-runtime-worker', not currently running on the Tokio runtime.C:\Users\janos\.cargo\registry\src\github.com-1285ae84e5963aae\tokio-0.2.23\src\runtime\handle.rs28' panicked at 'thread '', :C:\Users\janos\.cargo\registry\src\github.com-1285ae84e5963aae\tokio-0.2.23\src\runtime\handle.rs
not currently running on the Tokio runtime.tokio-runtime-workerC:\Users\janos\.cargo\registry\src\github.com-1285ae84e5963aae\tokio-0.2.23\src\runtime\handle.rs118:stack backtrace:
', ' panicked at '::118C:\Users\janos\.cargo\registry\src\github.com-1285ae84e5963aae\tokio-0.2.23\src\runtime\handle.rsnot currently running on the Tokio runtime.11828::', :
28118C:\Users\janos\.cargo\registry\src\github.com-1285ae84e5963aae\tokio-0.2.23\src\runtime\handle.rs28

It's weird for me that is says tokio-runtime-worker panicked and then not currently running on the Tokio runtime.

I'm using the default tokio feature from Iced:

[dependencies]
iced = { version = "0.2", features = ["image", "debug", "tokio"] }

Is there a migration process?
Could this error come from another crate conflicting with the Tokio version?

[yusdacra]

Enabling tokio-old instead of tokio should fix it. I also experienced the same problem since one of my crates is depending on tokio 0.2.

[janosimas]

I believe I found the issue, it's the crate reqwest: https://github.com/seanmonstar/reqwest/issues/1060