The given key 'Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope' was not present in the dictionary. about specflow.dependencyinjection

[Tuzi555]

I had the same issue and downgrading to version 3.9.2 of SolidToken.SpecFlow.DependencyInjection did the trick for me.

[rjvega]

@VladislavKutsTAQA Thanks for your report. I notice you are using Specflow 3.10.2-beta which introduces async features for the first time. I haven't tested the plugin against this beta version yet.

However the exception occurs in a piece of code that was rewritten in the last version, so would you be so kind to try using v3.9.2 of the SpecFlow.DependencyInjection plugin and see if it still happens?

This worked for me. Thanks

[mbhoek]

You don't need to downgrade SpecFlow (I see your tests are async) but can you please try to downgrade only the plugin SolidToken.SpecFlow.DependencyInjection to 3.9.2?

[mbhoek]

@VladislavKutsTAQA Thanks for your report. I notice you are using Specflow 3.10.2-beta which introduces async features for the first time. I haven't tested the plugin against this beta version yet.

However the exception occurs in a piece of code that was rewritten in the last version, so would you be so kind to try using v3.9.2 of the SpecFlow.DependencyInjection plugin and see if it still happens?

[VladislavKutsTAQA]

A can’t downgrade specflow version ***@***.*** Vladyslav Kuts Test Automation Engineer L2 Mobile: [phone] <tel:[phone]> LinkedIn<https://www.linkedin.com/in/%D0%B2%D0%BB%D0%B0%D0%B4%D0%B8%D1%81%D0%BB%D0%B0%D0%B2-%D0%BA-43b8a61a4/> Ushakova, Dnipro, 49061, Ukraine Timezone: (UTC+02:00) Working Remotely Timezone: (UTC+02:00) epam.com <http://www.epam.com> ***@***.*** CONFIDENTIALITY CAUTION AND DISCLAIMER This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies. From: Mark Hoek ***@***.***> Sent: Tuesday, June 7, 2022 2:26 PM To: solidtoken/SpecFlow.DependencyInjection ***@***.***> Cc: Vladyslav Kuts ***@***.***>; Mention ***@***.***> Subject: Re: [solidtoken/SpecFlow.DependencyInjection] The given key 'Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope' was not present in the dictionary. (Issue #88) @VladislavKutsTAQA<https://urldefense.com/v3/__https:/github.com/VladislavKutsTAQA__;!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWV-p_HvMV$> Thanks for your report. I notice you are using Specflow 3.10.2-beta which introduces async features for the first time. I haven't tested the plugin against this beta version yet. However the exception occurs in a piece of code that was rewritten in the last version, so would you be so kind to try using v3.9.2 of the SpecFlow.DependencyInjection plugin<https://urldefense.com/v3/__https:/github.com/solidtoken/SpecFlow.DependencyInjection/releases/tag/v3.9.2__;!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWV-elQyy-$> and see if it still happens? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/solidtoken/SpecFlow.DependencyInjection/issues/88*issuecomment-1148538080__;Iw!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWVzp4b2SU$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AYY5OX7A6EP3IU5P3LHN2WDVN4WVHANCNFSM5YB5L2RQ__;!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWVyRpF3jL$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[VladislavKutsTAQA]

All good! Thanks! ***@***.*** ***@***.*** ***@***.*** Vladyslav Kuts Test Automation Engineer L2 Mobile: [phone] <tel:[phone]> LinkedIn<https://www.linkedin.com/in/%D0%B2%D0%BB%D0%B0%D0%B4%D0%B8%D1%81%D0%BB%D0%B0%D0%B2-%D0%BA-43b8a61a4/> Ushakova, Dnipro, 49061, Ukraine Timezone: (UTC+02:00) Working Remotely Timezone: (UTC+02:00) epam.com <http://www.epam.com> ***@***.*** CONFIDENTIALITY CAUTION AND DISCLAIMER This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies. From: Mark Hoek ***@***.***> Sent: Tuesday, June 7, 2022 2:26 PM To: solidtoken/SpecFlow.DependencyInjection ***@***.***> Cc: Vladyslav Kuts ***@***.***>; Mention ***@***.***> Subject: Re: [solidtoken/SpecFlow.DependencyInjection] The given key 'Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope' was not present in the dictionary. (Issue #88) @VladislavKutsTAQA<https://urldefense.com/v3/__https:/github.com/VladislavKutsTAQA__;!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWV-p_HvMV$> Thanks for your report. I notice you are using Specflow 3.10.2-beta which introduces async features for the first time. I haven't tested the plugin against this beta version yet. However the exception occurs in a piece of code that was rewritten in the last version, so would you be so kind to try using v3.9.2 of the SpecFlow.DependencyInjection plugin<https://urldefense.com/v3/__https:/github.com/solidtoken/SpecFlow.DependencyInjection/releases/tag/v3.9.2__;!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWV-elQyy-$> and see if it still happens? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/solidtoken/SpecFlow.DependencyInjection/issues/88*issuecomment-1148538080__;Iw!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWVzp4b2SU$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AYY5OX7A6EP3IU5P3LHN2WDVN4WVHANCNFSM5YB5L2RQ__;!!GF_29dbcQIUBPA!xmjxks_vpX5euhLZYKlCXrAyehjIbNtm41FzxnqyPPem7dIVDJYb7xjbLK2tyI7KEZ1FChfbNZm79lSuPAiWVyRpF3jL$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[mbhoek]

Thanks for letting me know. I'll review the code and see if I can update it for the major version (v4).