Closed Qwin closed 6 years ago
This bug has been fixed with newer version of Xamarin.iOS 10.12.0.14. This issue can be closed.
@Qwin Really ? https://bugzilla.xamarin.com/show_bug.cgi?id=57919 says it is not fixed until 10.14.0.5 which will not be alpha for some time.
@graemechristie correct I thought it was fixed but it wasn't but u can see from the bug report you have linked I am the one that actually created that bug :)
My real name is Robertalmalak ;)
Assuming it is fixed for now and not directly a sink issue I m closing this issue. Feel free to reopen if we need to have a further look.
UPDATE: So after some testing and replacing the whole elasticsearch serializer with a custom one, I figured out the problem is indeed the dynamic dictionary (DynamicResponse) which uses dynamic type. This is not allowed by Xamarin.iOS. I am not sure what we could do to resolve this issue. Maybe provide a different implementation and allow users to have a boolean in settings "UseDynamicTypes" to choose if they want to use the dynamicresponse. I posted this issue at ElasticSearch.Net github as well.
Hi Everyone,
So my issue is that after using the latest elasticsearch sink plugin I am getting the following error:
` After doing some research I found out that ElasticSearch.Net is using internally some dynamic code generation that is causing this error. I am using LogShipper and the bulk api.
ElasticSearch.Net 5.4.0 ElasticSearch.Sink 5.3.0 Serilog 2.5.0
Mono: 5.2.0.196 Using Beta version of Xamarin.iOS: 10.12.0.12
So I am not sure who is at fault. I do know Xamarin.iOS doesn't support dynamic code generation. (see Xamarin.iOS limitation docs).