Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
both Android and iOS:
When I try to install the AWSSDK.S3 to access Amazon services, I get the following linker error when trying to build iOS:
Failed to resolve "System.Void Amazon.Runtime.Internal.Util.AESEncryptionPutObjectStream::.ctor(System.IO.Stream,System.Byte,System.Byte)" reference from "AWSSDK.Core, Version=220.127.116.11, Culture=neutral, PublicKeyToken=885c28607f98e604"
..Android build has a similar error.
I have the following libraries installed:
this appears to be a bug in AWSSDK.Core, but reporting here, because documentation here:
says to please submit bug report "...If your application only works with -nolink"...which is the case here.
feel free to close if this is an AWS bug not fixable by Xamarin
The issue here is that your application is linking out this item's constructor in the AWSSDK.Core library:
System.Void Amazon.Runtime.Internal.Util.AESEncryptionPutObjectStream::.ctor(System.IO.Stream,System.Byte,System.Byte)" reference from "AWSSDK.Core, Version=18.104.22.168, Culture=neutral, PublicKeyToken=885c28607f98e604"
Now, is this your fault? Not really, it's partially the Linker to blame for being too aggressive, but also that this library probably doesn't preserve it's members and thus the linker links these items out.
I would consider this to be a bug on the AWSSDK.Core end where the maintainer could do a better job preserving the code:
Otherwise you can always mark this as a linkskip item:
For a bit more information about why this happens, check out my blog on this topic:
I am marking this issue as NEEDINFO as we are missing a reproduction project that demonstrates this issue. Although this bug is a little old, we will need that to proceed investigation.
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!