When DependencyService is registered before PLC project calls for the method, it works well. However if it is called before the native project registers the method, Register method in Dependency service never works again
Please find a sample project in the below link:
https://github.com/rags217/DSTest
in step 7 message should be dependency2 is set
in step 7 message should be dependency2 is null
Version with issue: 2.5.0.280555
Last known good version: N/A
IDE: Xamarin Studio for Mac
Platform Target Frameworks:
Android: 8.0
Android Support Library Version: N/A
Nuget Packages:
Affected Devices: Samsung galaxy, LG variants
how is the dependencyservice supposed to know waht implementation to register? lets say i have IApi, and i have 2 implementations, one for the actual api, and one for fake data used for unit tests. The nice thing about DI is that i myself decide what to register, and for that I have to register it. Maybe i understood this the wrong way but this is how DI works imo.
is there a typo in Actual behaviour? you say that it should be somthing, but what is it?
Steps to reproduce makes no sense, did you mix up 1 and 2?
My apologies.
I have got it completely wrong from step 6. Below is the correct explanation:
* Expected Behavior*
in step 7 message should be -> dependency2 is called
* Actual Behavior*
in step 7 message -> dependency2 is null
Could you please tell me what version of Xamarin I can have this in a working state and when it will be released?
This issue doesn't seem to have had any activity in a long time. We're working on prioritizing issues and resolving them as quickly as we can. To help us get through the list, we would appreciate an update from you to let us know if this is still affecting you on the latest version of Xamarin.Forms, since it's possible that we may have resolved this as part of another related or duplicate issue. If we don't see any new activity on this issue in the next 30 days, we'll evaluate whether this issue should be closed. Thank you!
This issue doesn't seem to have had any activity in a long time. We're working on prioritizing issues and resolving them as quickly as we can. To help us get through the list, we would appreciate an update from you to let us know if this is still affecting you on the latest version of Xamarin.Forms, since it's possible that we may have resolved this as part of another related or duplicate issue. If we don't see any new activity on this issue in the next 30 days, we'll evaluate whether this issue should be closed. Thank you!
I can confirm that the issue is there in the latest version of Xamarin.Forms
Most helpful comment
Could you please tell me what version of Xamarin I can have this in a working state and when it will be released?