[External - Prism.DryIoc.Extensions] Authenticationhandler can only work on the last registered item？？？ about apizr HOT 5 CLOSED

Dan just pushed its container extensions packages on NuGet with multiple instance registration/resolution feature, witch finally fix this. Please make sur to update to at least v8.0.48

from apizr.

Hi @dorisoy ,

Actually, I noticed that behavior yesterday on my side.
Thank you for reporting it.
I have to fix that thing.

Expect a 1.5.1 nuget update probably tomorrow.

Regards

from apizr.

Ok I investigated.

First I tried to reproduce this bug in the mobile sample with two authenticated api interfaces.
Same config as yours, same error 401 as yours.
Then I tried with the console sample with all the same config but not the same result, as it returned me a success 200 for both api calls...?!!!

I found out that I was using MS DI with the console sample and DryIoc with the mobile one.
And guess what? Replacing DryIoc by MS DI in the mobile sample fixed the problem.

Actually, we're still talking about the same problem wich is #1, wich still comes from #124 on Prism.DryIoc.Extensions

Apizr makes use of AddHttpClient and AddTypedClient service collection official extensions wich register multiple implementation type for a same service type. This is not yet available using Prism.DryIoc.Extensions. That's what I'm talking about on my Readme notes.

Personally, my workaround is to use Prism.Microsoft.DependencyInjection.Extensions instead of Prism.DryIoc.Extensions.

Actually, waiting for this to be fixed and released on Nuget for DryIoc, you'd better download the Prism.Container.Extensions project as I did, fixe the MS DI NavigationService issue like I did in this not yet approved PR (only one line of code), and refrence this MS DI project directly into yours.

You'll get all working as excpected so far.

from apizr.

@JeremyBP
Well, as you said, Thank you for your contribution to this project and I will adopt the solution you suggest。

from apizr.

Dan just pushed its container extensions packages on NuGet with multiple instance registration/resolution feature, witch finally fix this. Please make sur to update to at least v8.0.48

@JeremyBP Thank you for sharing everything for open source !

from apizr.