Posts

• tranb3r FRMember ✭✭

  October 2016

  Any plan to release this change in the beta channel as well?

  0
• JeremyKolb USMember ✭✭✭

  October 2016

  I upgraded, loaded my android project and it's now changed the TargetFrameworkVersion to 7.0 without asking. That's a bug.

  0
• BrendanZagaeski USForum Administrator, Xamarin Team Xamurai

  October 2016

  Any plan to release this change in the beta channel as well?

  I believe that is exactly one of the pieces of information in the first post in the thread:

  The Cycle 8 – Service Release 1 version currently in the Beta channel includes additional fixes for those known issues, but it has not yet been updated for Xcode 8.1 compatibility. The Xcode 8.1 compatibility changes are in the process of being added to those builds for a refreshed Beta version as soon as possible.

  0
• BrendanZagaeski USForum Administrator, Xamarin Team Xamurai

  October 2016 edited October 2016

  That's a bug.

  ->

  Please file a quick bug report using the "Cycle 8" new bug form if you see any behavior that looks suspicious in these versions

  Thanks in advance!

  0
• JeremyKolb USMember ✭✭✭

  October 2016

  Please fix your release process. Document all the changes. Make sure that when you say you only fix xcode integration that's ACTUALLY the only thing that has changed.

  I'm now hitting https://bugzilla.xamarin.com/show_bug.cgi?id=43833 with the latest stable which means that SOMETHING else changed besides xcode 8.1 support. I love Xamarin but this is so frustrating.

  0
• BrendanZagaeski USForum Administrator, Xamarin Team Xamurai

  October 2016 edited October 2016

  Very sorry to hear you're seeing issues after updating. That's never fun. For reference, do note that the Xcode 8.1 support update didn't touch Xamarin.Android. One indication of this is for example that there is no Xamarin.Android package mentioned in the Release Blog post. Another indicator is that the commit hash of the version of Xamarin.Android included in the XamarinVS installer for Cycle 8 – Service Release 0 was 5a02b032, and that is the same commit hash included in this Xcode 8.1 support release. Consequently, Xamarin.Android would not have been explicitly tested for this release beyond a few basic checks to ensure the integrity of the files in the Xamarin.Android sub-package within the installer.

  Indeed, the bug you have linked (Bug 43833) appears to be a remaining known issue that is held over from the original Cycle 8 (September 13) feature release. It is interesting to hear that the behavior of that bug can apparently change between an earlier version of Cycle 8 and the current version. In principle one would expect the breakage to have been visible since the first Cycle 8 release back in September if it was ever going to appear. So it is surprising that Xamarin.Android would change behavior simply because it was repackaged in the XamarinVS installer alongside a newer version of Xamarin.iOS. On the other hand, it also probably is not quite logically provable that the change in re-packaging could not have affected Xamarin.Android, so many thanks for the bug report and any follow-up help on the investigation! The engineering team will be interested to look into what could have changed. My initial suspicion would be that the issue might have been caused by an unexpected change in your local project configuration. That change in turn might or might not involve some unique factors about your particular project or development environment.

  0
• JeremyKolb USMember ✭✭✭

  October 2016

  @BrendanZagaeski said:
  Consequently, Xamarin.Android would not have been explicitly tested for this release beyond a few basic checks to ensure the integrity of the files in the Xamarin.Android sub-package within the installer.

  Thanks for the quick reply.

  I think this gets to the heart of the issue right here. I know how much of a pain in the butt writing and runnings tests are but every release should be run through the full battery of tests. Maybe this problem is a local issue specific to my machine (though this did work last week on the previous stable) but the fact that you guys aren't running all of your (presumably written) tests because this change was only supposed to affect a small portion of the system is troubling.

  0
• BrendanZagaeski USForum Administrator, Xamarin Team Xamurai

  October 2016 edited October 2016

  ... the fact that you guys aren't running all of your (presumably written) tests ...

  Unfortunately it's not quite that simple. The absolute full testing pass is expensive in terms of time and resources, and Xamarin of course only has finite resources and time, so there are ripple effects to consider for other in-progress work. That's also not to mention the unavoidable fact that sometimes (such as this time), the GM Xcode version includes new changes compared to the previous beta version, and if Xamarin doesn't release quickly to cover those differences, then the relative area of effect on user experience could be greater than other unpredicted (and unprecedented) side effects of the re-packaging process. In short, there are trade-offs in every direction, and optimizing those trade-offs is unfortunately not trivial.

  0
• JKay USMember ✭✭✭

  November 2016 edited November 2016

  Has anyone else had trouble deploying to Android 7 devices?

  I'm deploying to a Nexus 9 running Android 7. First deploy works fine. Second deploy doesnt launch and returns:

  11-08 10:03:55.238 E/mono-rt ( 4552): Stacktrace:
  11-08 10:03:55.238 E/mono-rt ( 4552):
  11-08 10:03:55.238 E/mono-rt ( 4552): at <0xffffffff>
  11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.VisualElementRenderer1<TElement_REF>.SetElement (TElement_REF) [0x000ae] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:175 11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.VisualElementRenderer1.Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement) [0x00027] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:126
  11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement) [0x0001f] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\Platform.cs:289
  11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.Platform.AddChild (Xamarin.Forms.VisualElement,bool) [0x00015] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\Platform.cs:526
  11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.Platform.SetPage (Xamarin.Forms.Page) [0x00089] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\Platform.cs:414
  11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.FormsApplicationActivity.InternalSetPage (Xamarin.Forms.Page) [0x000b7] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:288
  11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.FormsApplicationActivity.SetMainPage () [0x00000] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:307
  11-08 10:03:55.238 E/mono-rt ( 4552): at Xamarin.Forms.Platform.Android.FormsApplicationActivity.LoadApplication (Xamarin.Forms.Application) [0x0003f] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:110
  11-08 10:03:55.238 E/mono-rt ( 4552): at FieldStrikeMove.Droid.MainActivity.OnCreate (Android.OS.Bundle) [0x00026] in \tfs\FieldStrike\FieldStrikeMove\FieldStrikeMove.Droid\MainActivity.cs:73
  11-08 10:03:55.238 E/mono-rt ( 4552): at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (intptr,intptr,intptr) [0x00011] in /Users/builder/data/lanes/3819/5a02b032/source/monodroid/src/Mono.Android/platforms/android-23/src/generated/Android.App.Activity.cs:2426
  11-08 10:03:55.239 E/mono-rt ( 4552): at (wrapper dynamic-method) object.b2b86004-790b-4380-8785-35d76a9324c6 (intptr,intptr,intptr)
  11-08 10:03:55.239 E/mono-rt ( 4552): at (wrapper native-to-managed) object.b2b86004-790b-4380-8785-35d76a9324c6 (intptr,intptr,intptr)
  11-08 10:03:55.239 E/mono-rt ( 4552):
  11-08 10:03:55.239 E/mono-rt ( 4552): Attempting native Android stacktrace:
  11-08 10:03:55.239 E/mono-rt ( 4552):
  11-08 10:03:55.240 E/mono-rt ( 4552): Could not unwind with libunwind.so: dlopen failed: library "/data/app/eu.fieldstrike.android.fieldstrike-1/lib/arm/libunwind.so" not found
  11-08 10:03:55.240 E/mono-rt ( 4552): Could not unwind with libcorkscrew.so: dlopen failed: library "/data/app/eu.fieldstrike.android.fieldstrike-1/lib/arm/libcorkscrew.so" not found
  11-08 10:03:55.240 E/mono-rt ( 4552):
  11-08 10:03:55.240 E/mono-rt ( 4552): No options left to get a native stacktrace :-(
  11-08 10:03:55.240 E/mono-rt ( 4552):
  11-08 10:03:55.240 E/mono-rt ( 4552): =================================================================
  11-08 10:03:55.240 E/mono-rt ( 4552): Got a SIGSEGV while executing native code. This usually indicates
  11-08 10:03:55.240 E/mono-rt ( 4552): a fatal error in the mono runtime or one of the native libraries
  11-08 10:03:55.240 E/mono-rt ( 4552): used by your application.
  11-08 10:03:55.240 E/mono-rt ( 4552): =================================================================
  11-08 10:03:55.240 E/mono-rt ( 4552):

  I am using Shared Runtime

  0