›

Stable Channel: Cycle 8 – Service Release 0

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited October 2016 in General

Please see https://releases.xamarin.com/stable-release-cycle-8-service-release-0/ for the details about this release, including the steps to update or downgrade as needed.

Bug reports wanted!

  • Please file a quick bug report using the "Cycle 8" new bug form if you see any behavior that looks suspicious in these versions (and if it isn't clear whether one of the known issues in the release notes matches the problem).

    • If you get any errors when using the form to submit, please select the All Products option and choose the desired product.

  • Comment in this forum thread if your question is not related to a suspicious behavior after installation, but instead one of the following:

    • You notice an error in the Release Blog post.
    • You have trouble downloading one of the installer packages.

Remaining higher-visibility known issues from the list for the previous release

  • [Xamarin for Visual Studio], [Xamarin Studio] - 43566 - The iOS Designer initialization process will cause any running iOS 10 simulator to become non-responsive. The designer initialization happens when opening an iOS project in Xamarin Studio and during the connection to the remote Mac in Visual Studio. This issue does not affect Xcode 7.3, iOS 9.3 (and lower) simulators.

    • Improved in this release: Cycle 8 Service Release 0 includes some fixes to reduce the chances of hitting this problem, but additional fixes are also planned.

    • Workaround: Quit and restart the simulator after the designer has initialized. You can then proceed to use the simulator again as normal.

Open bugs list

You can view all of the remaining bugs that have been reported against the Cycle 8 version that are not yet fixed in "Cycle 8 – Service Release 0" using the following Bugzilla query:

Some higher-visibility known issues from the open bug list

  • [Xamarin for Visual Studio] - 44300 - Xamarin.Android projects appear as "Incompatible" after closing and reopening a solution in a single VS session. Visual Studio's ActivityLog.xml file shows "LegacySitePackage failed for package [XamarinAndroidPackage] ... Method not found: ... Mono.AndroidTools.AnalyticsService.ReportContextProperty(System.String[], System.String[]) ...".

    • Updated Oct 04: A candidate fix for this issue has now been published to the Stable channel in version 4.2.0.703. A potential remaining issue involving Test Recorder remains under investigation, so it is recommended to uninstall Test Recorder if you continue to see this issue after the update.

    • Old partial workaround: Deleting the contents of %LOCALAPPDATA%\Microsoft\VisualStudio\14.0\ComponentModelCache and then closing and opening Visual Studio again will allow the Android project to load. Note that closing and re-opening the solution again in this new session can cause the issue to re-occur.

  • [Xamarin Studio] - 44285 - Xcode 8 quits after Xamarin Studio returns to the foreground when using Xcode 8 via Open With > Xcode Interface Builder.

  • [Xamarin.Android] - 44633 - "Deployment failed because of an internal error: Failure [INSTALL_FAILED_DEXOPT]" when <AndroidUseSharedRuntime> is enabled in certain projects because classes.dex is not deployed to device as expected.

  • [Mono], [Xamarin.iOS], [Xamarin.Android], [Xamarin.Mac] - 44708 - "TrustFailure (The authentication or decryption has failed.) ... Invalid certificate received from server." with "Error code: 0x5" or "Error code: 0xffffffff800b010f" when attempting to access HTTPS servers on ports other than 443

    • Updated Oct 04: A candidate fix for this issue has now been published to the Stable channel in Mono 4.6.1.5, Xamarin.iOS 10.0.1.10, Xamarin.Android 7.0.1.3, Xamarin.Mac 2.10.0.105, and Xamarin for Visual Studio 4.2.0.703.

  • [Xamarin for Visual Studio] - 44535 - "'System.ComponentModel.INotifyPropertyChanged' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.ObjectModel" for projects that reference PCLs with INotifyPropertyChanged

EDIT Sep 28: Add some higher-visibility known issues from the open bug list.
EDIT Oct 04: Update for new builds that includes candidate fixes for 44300, 42443, and 44708.

Tagged:

Posts

  • WilliamSRodzWilliamSRodz BRInsider, University, Developer Group Leader ✭✭

    @BrendanZagaeski just updated to this release and still getting the error related to

    [Xamarin.Android] – 44633 – “Deployment failed because of an internal error: Failure [INSTALL_FAILED_DEXOPT]” when is enabled in certain projects because classes.dex is not deployed to device as expected.

    do you have any info about this?

  • NMackayNMackay GBInsider, University mod
    edited October 2016

    When switching from Android to UWP and compiling to a physical device using ARM Visual Studio crashes.

    Error Handler Exception: System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.PipeException: There was an error reading from the pipe: Unrecognized error 109 (0x6d).
   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)
   --- End of inner exception stack trace ---
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ConnectionStream.EndRead(IAsyncResult asyncResult)
   at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
   --- End of inner exception stack trace ---
   at System.Net.Security.NegotiateStream.EndRead(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.StreamConnection.EndRead()
   --- End of inner exception stack trace ---
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext) \r\n    at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)

the message resource is present but the message is not found in the string/message table

    VS2015 SP3

    Xamarin 4.2.0.698 (016ed17)
    Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

    Xamarin.Android 7.0.1.2 (c1d1c79)
    Visual Studio extension to enable development for Xamarin.Android.

    Xamarin.iOS 10.0.0.1 (29910bb)
    Visual Studio extension to enable development for Xamarin.iOS.

  • JonDouglasJonDouglas USXamarin Team, University, Developer Group Leader Xamurai
    edited October 2016

    @WilliamSRodz I have replied to your same question here:

    https://github.com/xamarin/xamarin-android/pull/236

    It is slated for SR 1 currently as per the Bugzilla Target Milestone status.

    If you needed to workaround this right now, you can edit your Xamarin.Android.Common.targets directly with the new committed fix:

    https://github.com/dellis1972/xamarin-android/blob/7757dc4f48e62f9d8a00750e9516d0fcbe814f59/src/Xamarin.Android.Build.Tasks/Xamarin.Android.Common.targets

    However it is not advisable to do this directly and rather you should wait on the release if you can. (Or just keep a copy of that targets file handy to revert back to)

  • TomPeerTomPeer USMember ✭✭
    edited October 2016

    With Android SDK from Version 4.2.0.703 I get this error:

    [] cant resolve internal call to "System.Threading.Monitor::enter_with_atomic_var(object,bool&)" (tested without signature also)
    [mono]
    [mono] Your mono runtime and class libraries are out of sync.
    [mono] The out of sync library is: /data/data/com.companyname.uitests/files/.override/mscorlib.dll

    I don't know how I can describe this in a bug report.

    If I downgrade to Version 4.1.2.18 all works fine again.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited October 2016

    I don't know how I can describe this in a bug report.

    See https://developer.xamarin.com/guides/cross-platform/troubleshooting/questions/howto-file-bug/. To re-summarize:

    • If you haven't already, you can run a quick Bugzilla search (and web search) to double-check that there aren't any answers about the issue yet.

    • Include the same content as your forum message, which covers: (a) a description of what happened (the error message you pasted in this forum) and (b) what was expected to happen (your description that downgrading caused the error to stop is sufficient).

    • Include a description of the steps you followed to see the problem, including if at all possible a self-contained test case that reproduces the bug with as little code as possible. Bugs with test cases will often be resolved more quickly than bugs without test cases.

    • Include your detailed version information for your operating systems, Xamarin, and Android.

    Thanks in advance!

    Side note, for this particular problem, I'd recommend trying manually uninstalling the app from the Android device and then redeploying.

  • NMackayNMackay GBInsider, University mod

    @BrendanZagaeski

    HTTPS issues and Android project incompatibility sorted, appreciate your efforts in getting these issues escalated.

  • YhANYhAN USMember ✭
    edited October 2016

    Installer Keep telling Network is not reachable but Most Servers is reachable 

    [2016-10-06 03:38:16.537] [Info] No network connectivity. Falling back to embedded manifest. Software might be older versions than currently published!

    I do want know which server you used to test the network connectivity, since the www.xamarin.com download.xamarin.com d13lzi7g5dqad4.cloudfront.net dl.google.com is reachable while running the installer.

    echo %JAVA_HOME%
d:\Dev\Jdk7

echo %ANDROID_HOME%
d:\Dev\Android\sdk

    Android SDK installed
    JDK 1.7 installed
    Xamarin.VisualStudio_4.1.0.530 installed
    manually

This discussion has been closed.