Bug Annotations for XamarinVS

Bug
(Priority)
ProductsSummaryBroken Since
(Known Working)
Fixed on StableFixed on BetaFixed on AlphaAdditional Status
Filter Filter Filter Filter Filter
Non-public 36117 (High)
  • XamarinVS
  • iOS

Certain distribution provisioning profiles do not appear in the iOS project settings.

Possible temporary workaround: The problem is limited to browsing the provisioning profiles. If you set the desired "CodesignProvision" and "CodesignKey" using Xamarin Studio on Mac, the values will be preserved in the project file, and the app will be signed correctly when building in Visual Studio on Windows. Similarly, if you set the desired provisioning profile on Mac, save the project, and then open the .csproj file in a text editor, you can find the <CodesignProvision> and <CodesignKey> elements, and then copy them into the corresponding location in the .csproj file on Windows.

  • XamarinVS 4.0.0.1689
    (3.11.1594)

Candidate patch committed. Fix planned for Stable release in "Cycle 6 – Service Release 1" (winter 2015 – 2016).

Non-public 35956 (High)
  • XamarinVS
  • iOS

The application XXXXXX needs to be rebuilt due to an inconsistency between the connected Mac and the local app. Please rebuild the application and try again.

This error is expected after upgrading from Xamarin 3 to Xamarin 4 until a clean build is performed.

Steps that would in theory be expected to stop the problem (but might fail as reported in Bug 35956):

  1. Clean the project while connected to the build host.
  2. Manually delete the bin\ and obj\ folders on Windows and the $HOME/Library/Caches/Xamarin/mtbs folder on Mac.
  3. Manually remove any previously installed versions of the app from the device (or use the "Simulator -> Reset Content and Settings" menu item if running on a simulator).

Possible partial workarounds in case those steps fail:

  • Explicitly disconnecting and reconnecting the Mac build host has been reported to help in one case.

  • Another possible (though inconvenient) workaround from that same forum thread is to:

    1. Create a new project, and then re-import all of the existing resources and files from the old project.
    2. Build the project on the command line using MSBuild.
    3. Debug the app from Visual Studio (without rebuilding).
  • XamarinVS 4.0.0.1689
    (3.11.1594)

Under investigation.

35786 (High)
  • XamarinVS
  • iOS

"error : Could not strip assembly" when attempting to build in a non-debug configuration with Visual Studio or with xbuild on Mac.

Partial workaround: Build the application in Xamarin Studio on Mac.

  • Xamarin.iOS 9.2.1.50
  • XamarinVS 4.0.0.1685

Candidate patch committed. Fix planned for Stable release in "Cycle 6 – Service Release 1" (winter 2015 – 2016).

Known Limitation (Normal)
  • XamarinVS
  • iOS

"Invalid credentials. Please try again." when attempting to log into the build host using an account "Full name" that includes an accented character. This appears to be a limitation of the SSH.NET library.

"Invalid credentials" in XamarinVS SSH login dialog caused by accented "é" in user name

Workaround: Use the "Account name" instead ("testuser" rather than "Test Usér" in this example). One way to find the "Account name" is to Control-click the user name in "System Preferences -> User & Groups" and select "Advanced Options".

Mac System Preferences for a username that includes an accented character

  • XamarinVS 4.0.0.1685

    (N/A, new feature)

No changes planned. Please use the "Account name" to log in as described in the Workaround.

Non-public 35945 (Normal)
  • XamarinVS
  • iOS

A docsync.log file appears in the current iOS solution directory after VS connects to the Mac build host. The file can safely be deleted.

  • XamarinVS 4.0.0.1689
    (3.11.1594)

Under investigation.

35858 (Normal)
  • Android
  • XamarinVS

In certain projects variable names may appear as "?" in the "Locals" window, and "Unknown identifier" may be displayed when hovering over the variables. The problem might be specific to async methods.

  • XamarinVS 3.11.1594

Under investigation.

Non-public 35750 (Normal)
  • XamarinVS

The .msi installer for XamarinVS attempts to use the disk with the most free space for temporary storage. This can cause various errors such as "Could not set file security for file … Verify that you have sufficient privileges to modify the security permissions for this file."

  • XamarinVS 4.0.0.1685

Under investigation.

32988 (Normal)
  • Xamarin.​Forms
  • XamarinVS

Modifying XAML files causes IntelliSense for references to other PCLs to fail in the ".xaml.cs" codebehind files with errors of the form "are you missing an assembly reference?"

  • Xamarin.​Forms 1.4.4

    (1.4.3)

Under investigation.

34932 (Low)
  • XamarinVS
  • iOS

If the Mac build host is connected to a router that has no access to the internet (or another DNS server that times out during the reverse-DNS lookup of the Windows PC), then Visual Studio will take roughly 30 seconds to retrieve the SSH fingerprint, and eventually fail to connect. The dialog error and the "Output -> Xamarin" Window will show the generic error message: "Couldn't connect to … Please try again."

Possible workaround, only recommended for users who know what this configuration change does: Add the following line to /etc/sshd_config:
UseDNS no

  • XamarinVS 4.0.0.1685
    (3.11.1594)

Candidate patch committed. Fix planned for Stable release in "Cycle 6 – Service Release 1" (winter 2015 – 2016).