Beta Release: Cycle 7 Feature Release Preview

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

This thread has now been closed to direct all further updates about this release onto the latest announcement:

http://forums.xamarin.com/discussion/65486/beta-release-cycle-7-feature-release/p1


Release Blog post: https://releases.xamarin.com/beta-cycle-7/

This is a feature release. A few of the early preview features are:

Known issues

See the Release Blog post and the individual per-product release notes for some of the documented known issues.

Bug reports wanted!

Please file a bug for any new issue you find in these Cycle 7 versions that you would like the Xamarin team to investigate. Note that Beta versions have not yet completed the full suite of tests by the Xamarin QA team. That said, customer bug reports are still much appreciated, even if the problem would eventually be caught by the remaining QA tests.

Installing the Beta and switching back to Stable

You can install this new Beta version or switch back to the current Stable version by changing updater channels.

Release info

Windows

  • Xamarin.VisualStudio_4.1.0.313.msi (514438c) Release Notes
  • XamarinStudio-6.0.0.4968.msi (ab7092c) Release Notes
  • gtk-sharp-2.12.33.msi

Mac

Release Blog post including estimated timeline to Stable: https://releases.xamarin.com/beta-cycle-7/

See the first entry in the release blog and "Xamarin Release Cycles" for more information about "cycles," "service releases," and "feature based releases."

Posts

  • NealCulinerNealCuliner USBeta ✭✭✭

    My app that uses Core Data won't launch at all in the SIM. I have not tried the device. My other app (iOS) works fine it seems, it's a more basic app using SQLite-net and MonoTouch.Dialog.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    Please file a quick new bug report for any suspected defects in these new versions. The initial report can be as simple as copy-pasting your forum comment word-for-word into the description. Thanks in advance.

  • NealCulinerNealCuliner USBeta ✭✭✭

    I sure did and am working with @SebastienPouliot but it's hard to get any good info so far but I will keep trying.

  • SebastienPouliotSebastienPouliot CAXamarin Team Xamurai

    Anyone with more information about the simulator issue should add it to this linked bug report. Thanks!

  • EricSchmeckEricSchmeck DEMember ✭✭

    And again I get this error:
    "Module Java.Interop, Version=0.1.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065' should be referenced"
    as I already mentioned here:
    http://forums.xamarin.com/discussion/comment/182857/#Comment_182857

    However, I am able to build my project without referencing this Java.Interop.

  • NealCulinerNealCuliner USBeta ✭✭✭

    Well, it's feedback, sorry it's negative. I do NOT like the new white icon with rose/red/pinkish edges. I do like the one when it knows I'm in DARK UI. I prefer the prior BLUE XS icon over the white one.

  • mustimusti USMember

    When will the WatchOS 2 supported?

  • GavinGrantGavinGrant GBUniversity ✭✭✭

    +1. Seriously Xamarin, when IS the WatchOS 2 going to be supported for a device?

  • vinguanvinguan USMember ✭✭

    +2 Seriously Xamarin, Is WatchOS 2.x will ever be supported? I really need to do a native watch app with Digital Crown and all the cool stuff. I'm stuck with a WatchKit Extension right now...

  • xCyborgxCyborg USMember ✭✭

    Direct link to XamarinVS please.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    "Module Java.Interop, Version=0.1.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065' should be referenced"
    However, I am able to build my project without referencing this Java.Interop.

    @EricSchmeck, now that we're a bit further into the release process, I'll recommend that you do go ahead and file a quick new bug report for that issue. The initial report can be as simple as copying and pasting the two lines I've quoted above into the description.

    If by chance you are able to cut down your full app to a small test case that still shows the problem, please do attach that test case on the bug report too. If you don't get a chance to do that minimization process, then if you can provide just your .csproj file and the diagnostic MSBuild output on the bug report, that would be perfect. Thanks in advance!

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    Direct link to XamarinVS please.

    In case any other users have the same question, I followed-up on it with xCyborg in another thread: http://forums.xamarin.com/discussion/comment/191671/#Comment_191671.

  • MichaelRumplerMichaelRumpler ATMember ✭✭✭✭✭
    edited April 2016

    It seems like the cycle 7 causes bug #38982 "Android app hangs" for me. I don't have that problem when I go back to the stable channel which installs XamarinVS 4.0.3.214.

  • BenjaminTrautBenjaminTraut USMember

    Any chance to offer a direct download link to the .msi-offline-installer for Xamarin Studio, perhaps in the Download-section of the account? In our company we do not have direct access to the internet, so using a different update-channel is unfortunately a no-go.

    Thanks!

  • mustimusti USMember

    @vinguan said:
    +2 Seriously Xamarin, Is WatchOS 2.x will ever be supported? I really need to do a native watch app with Digital Crown and all the cool stuff. I'm stuck with a WatchKit Extension right now...

    I guess no more WatchOS apps from Xamarin will end up on the AppStore. WatchOS 2 is going to be required.
    https://developer.apple.com/news/?id=04222016a

  • vinguanvinguan USMember ✭✭

    @musti said:

    @vinguan said:
    +2 Seriously Xamarin, Is WatchOS 2.x will ever be supported? I really need to do a native watch app with Digital Crown and all the cool stuff. I'm stuck with a WatchKit Extension right now...

    I guess no more WatchOS apps from Xamarin will end up on the AppStore. WatchOS 2 is going to be required.
    https://developer.apple.com/news/?id=04222016a

    Now they have to provide this supports until this date. We re gonna have to go native if they cant do it.

  • mustimusti USMember

    @vinguan said:

    @musti said:

    @vinguan said:
    +2 Seriously Xamarin, Is WatchOS 2.x will ever be supported? I really need to do a native watch app with Digital Crown and all the cool stuff. I'm stuck with a WatchKit Extension right now...

    I guess no more WatchOS apps from Xamarin will end up on the AppStore. WatchOS 2 is going to be required.
    https://developer.apple.com/news/?id=04222016a

    Now they have to provide this supports until this date. We re gonna have to go native if they cant do it.

    I sure hope so.

  • AdrianKnightAdrianKnight USMember ✭✭✭✭

    @BrendanZagaeski I'm getting the attached exception when I scroll up and down on a ListView with a large item collection. This is raised in a Forms app, but I think this is a cycle 7 issue. Each view cell is relatively small in height. On an S6 device, I load 8 of them upon page load so I'm not sure if it's too much for Mono to push many items in and out of view surface quickly.

    This issue is similar to:
    https://bugzilla.xamarin.com/show_bug.cgi?id=39189
    http://stackoverflow.com/a/10603714

  • AdrianKnightAdrianKnight USMember ✭✭✭✭

    I should add the issue is raised if each view cell has an image. Text-only listview items do not have this problem.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    When will the WatchOS 2 supported?

    I asked the team about this. Updating the watchOS 2 preview to add bitcode support is a high priority. It is among the top priorities the engineering team will be working on after this week's Evolve conference. Apple's recent announcement that watchOS 2 will be required for all new watchOS app submissions starting in June is definitely on the minds of the engineering team.

    The hope is that a preview with bitcode support can be made available by the end of May, but the team is still wary of any unanticipated complications that could change that timeline.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited April 2016

    Any chance to offer a direct download link to the .msi-offline-installer for Xamarin Studio

    @BenjaminTraut, for the time being I'd say the simplest way to get individual installer links for pre-Stable versions would be to request them via a quick email to contact@xamarin.com.


    EDIT: Correct Markdown.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    @AdrianKnight, if Bug 39189 already includes a test case that demonstrates the new problem, that's perfect. Just be sure to mention the complication about the potential involvement of Cycle 7 on that bug report. Otherwise, when you get a chance please do submit a new bug report against Cycle 7, being sure to copy the description of the problem from your forum comment into the description and also being sure to attach a minimal test case that demonstrates the problem.

    Thanks in advance!

  • AdrianKnightAdrianKnight USMember ✭✭✭✭

    @BrendanZagaeski I'm not 100% convinced that this is a Cycle 7 issue to be honest. I think it was probably with Mono for a very long time. I created a new bug with a repro. Hope this can be solved quickly.

    Here's the new bug: https://bugzilla.xamarin.com/show_bug.cgi?id=40692

  • infoMantisinfoMantis DEUniversity ✭✭

    @AdrianKnight @BrendanZagaeski We didn't have that problem before updating to Cycle 7.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    This thread has now been closed to direct all further updates about this release onto the latest announcement:

    http://forums.xamarin.com/discussion/65486/beta-release-cycle-7-feature-release/p1

This discussion has been closed.