Deploy and debug your app on emulators and devices, using the simplest and most cost-effective method for your needs.Hi all, it's about a year that my solution don't compile in Visual Studio Mac after update to the last tools version (VS Mac, Xamarin, etc).Visual Studio for Mac distributes updates for the IDE and supported frameworks on a regular basis.Also, Xamarin fully supports Android Wear. Xamarin project structure. Most of the Xamarin-related work is expected to be run via a Windows development computer with Visual Studio and Xamarin installed.I have installed Xamarin iOS on windows for VS, plus on the Mac, I have necessary license for Xamarin. I'm using Unity 2018.2.6f1 and Visual Studio Community for Mac 7.4.3 (build 10).10 minutes + download/installation time. A mobile app for Android and iOS that displays a 'Hello World' message.Installation UUID: dc3ea371-1dfd-400c-b88f-a7d708ad2940Mono 5.12.0.309 (2018-02/39d89a335c8) (64-bit)Xamarin.Mac 4.4.1.178 (master / eeaeb7e6) Package version: 512000309SDK: /usr/local/share/dotnet/sdk/2.1.302/SdksMSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.12.0/lib/mono/msbuild/15.0/bin/SdksLocation: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin ProfilerVersion: 8.3.3.2 (Visual Studio Professional)Android SDK: /Users/michelangelo/Library/Developer/Xamarin/android-sdk-macosxJava(TM) SE Runtime Environment (build -b11)Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)Android Designer EPL code available here:Version: 5.0.0.0 (Visual Studio Professional)Version: 12.2.1.10 (Visual Studio Professional)Git revision: d7cd66f5e3acd3d46ba0b94a0c935378f828bde0Xamarin extensions: bc9b985bfcb480b04a208a6d4045adc443a07857Darwin 17.7.0 Darwin Kernel Version 17.7.0Root:xnu-4570.71.2~1/RELEASE X8664 x86_64= Enabled user installed extensions =Probably is for this that my iOS solution don't compile anymore, instead of Android compile done./Library/Frameworks/Mono.framework/Versions/5.12.0/lib/mono/msbuild/15.0/bin/Roslyn/Microsoft.CSharp.Core.targets(5,5): Error: System.ComponentModel.Win32Exception (0x80004005): ApplicationName='mcs.exe', CommandLine=' /noconfig w0000gn/T/tmpa4105c6203ca459eba1c69f42a3a9005.rsp"', CurrentDirectory='', Native error= Cannot find the specified fileAt System.Diagnostics.Process.StartWithCreateProcess (System.Diagnostics.ProcessStartInfo startInfo) in /Users/builder/jenkins/workspace/build-package-osx-mono/2018-02/external/bockbuild/builds/mono-x64/mcs/class/System/System.Diagnostics/Process.cs:775At System.Diagnostics.Process.Start () in /Users/builder/jenkins/workspace/build-package-osx-mono/2018-02/external/bockbuild/builds/mono-x64/mcs/class/referencesource/System/services/monitoring/system/diagnosticts/Process.cs:2005At (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start()At Microsoft.Build.Utilities.ToolTask.ExecuteTool (System.String pathToTool, System.String responseFileCommands, System.String commandLineCommands) in //src/Utilities/ToolTask.cs:862At Microsoft.CodeAnalysis.BuildTasks.ManagedCompiler.ExecuteTool (System.String pathToTool, System.String responseFileCommands, System.String commandLineCommands) in :0 (ENSoft.iOS)For information, this is the error I have when build solution:/Library/Frameworks/Mono.framework/Versions/5.12.0/lib/mono/msbuild/15.0/bin/Roslyn/Microsoft.CSharp.Core.targets(5,5): Error: System.ComponentModel.Win32Exception (0x80004005): ApplicationName='mcs.exe', CommandLine=' /noconfig CurrentDirectory='', Native error= Cannot find the specified fileAt Microsoft.Build.Utilities.ToolTask.ExecuteTool (System.String pathToTool, System.String responseFileCommands, System.String commandLineCommands) in /_/src/Utilities/ToolTask.cs:862At Microsoft.CodeAnalysis.BuildTasks.ManagedCompiler.ExecuteTool (System.String pathToTool, System.String responseFileCommands, System.String commandLineCommands) in :0 (ENSoft. Visual Studio for Mac provides two channels to get these latest versions: Stable - Provides thoroughly tested updates. This channel is recommended for the best.
The beta for that solution has been available for quite some time.One would have expected that Xamarin would make sure that their product is compatible before the Xcode publication, so that developers don't get stuck with broken tools. Whilst there might be some highly emotional language being used, it's not defensible to argue that Xamarin has only had a few days to make sure their product is compatible with the 9.3 Xcode. The Simulator is set to iPhone 6.1. Dictation is not working in microsoft word for macIn the absence of any clear guidance from Xamarin, why wouldn't they go for it?I'm advocating a simple status page shows their readiness with respect to the various SDKs available. Had Xamarin made it clear to everyone that there was an issue, and not to download Xcode 9.3, then this problem could have been avoided.User7713 indeed experience shows it's a good idea to wait - particularly with Xamarin tools.However, there are plenty of developers who aren't just rushing - they really do need to get code built with the latest SDK features. We're often the ones who find out that things don't work well, which results in developer downtime. I pay for an Enterprise version of the tools and I'm finding they are broken far too often.If we treated our customers in this way, we wouldn't have too many customers for too long.And even if, for good technical reasons, the above is not possible, then Xamarin should make the position clear to their developers. This has become the norm and it's not acceptable. Cannot Check Ios In Visual Studio Upgrade To EachThey update without understanding the potential risks involved.I think people understand the risks and often the problem is simply caused by the autoupdate which is on by default. Yes I'll update immediately'. It doesn't of course - but it certainly does feel like it when you've spent a working day trying to get your tools working again.It just amazes me that so many people might go 'oh there is a new XCode version out that I rely on to build iOS apps. It's almost a 'no effort' solution and would go a long way towards answering many complaints that "this sort of thing happens every time". Red - don't do it.If Xamarin could maintain such a thing then every developer would know if it's OK to upgrade to each new version of iOS or Android (or other) SDKs and could largely avoid these issues. Yellow - OK but with a workaround. You can find the support you need for Xcode 9.3 here:Apple released 9.3 on Thursday, and while we could have released something right away, we wanted to run all of our tests against the official 9.3 to make sure we did not ship something broken. It is a complete mess from my point of view.We have been publishing support for Xamarin to support Xcode 9.3 since the beta process started, so we have been tracking every change from Apple. Issues like this one do happen to Xamarin maybe not regularly, but more often than expected, development itself is unnecessarily complex (more complex than with native approach, because you need to take care of the same things as when doing it natively plus the Xamarin part), tools are worse than those available for Java/Obj-C (Android Studio and AppCode) and unless you're doing something really simple, you need to code it twice, because there's no usable abstraction you could use for iOS and Android. Can't really see a good reason to use it. They also didn't take any steps to warn their users.Overall, I'm hugely disappointed with Xamarin. (At the least, I think the finding that the releases.xamarin.com page (with an RSS feed) does not provide sufficient visibility suggests that adding another status web page might not be the optimal approach, so something with more of a push-style notification would be better.)(Cross-reference. Emails are a possibility too, but I'm in favor of something in-product if we can make that work. So I put it away the current one (that had other problems), restarted from the scratch the app and voila', unable to load the code on the iPhone (again, the emulators works).I installed the latest Xamarin code available and this is my environment (on Mac)Installation UUID: 3a616150-13b4-44d3-9f8e-cc823c771004Mono 5.10.0.179 (2017-12/dac60775616) (64-bit)Xamarin.Mac 4.4.0.36 (master / 0c7c49a6) Package version: 510000179SDK: /usr/local/share/dotnet/sdk/2.1.4/SdksMSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.10.0/lib/mono/msbuild/15.0/bin/SdksLocation: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin ProfilerVersion: 4.4.0.31 (Visual Studio Community)Version: 11.10.0.32 (Visual Studio Community)Version: 8.3.0.5 (Visual Studio Community)Android SDK: /Users/xxxxxxxxxxxxx/Library/Android/sdkJava(TM) SE Runtime Environment (build -b11)Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)Git revision: ace1e107c88477db1abe5e807809650f064112c4Xamarin addins: a01263bdbba2589b1f6e42ef085bd31f6e3bfcf4Darwin 17.5.0 Darwin Kernel Version 17.5.0Root:xnu-4570.51.1~1/RELEASE X8664 x86_64Internet of Things (IoT) development (Preview) 7.1Why the emulator works and the real device is not ?I would expect ANY device/emulator to experience the problem if it was a Xcode 9.3 issue.In other words, what the difference between emulators and real iPhone regarding the presence of the framework ?Is it possible to manually load the framework on the correct place for the iPhone ?As a note, I have started a discussion with the Xamarin.iOS team to recommend that Xamarin.iOS and Visual Studio provide a warning to users when a new incompatible version of Xcode is released on the App Store before the current version of Xamarin.iOS and Visual Studio is compatible with that version. " but ONLY if I try to load the compiled code on a real device.And what is strange is that I did update Xcode days ago and everything worked until this morning.What I had to do this morning was to start the Xamarin project from a known github release. You can get these builds here:We are exploring ways to mitigate scenarios where users upgrade their SDKs before we ship our full support, and we hope to bring those to upcoming releases.I'm having the same problem, updated to Xcode 9.3 (for other reasons I needed to have Xcode updated) and now I have the error "error HE0003: Could not load the framework 'DADocSetAccess'. So I told the team to wait until this week to release.The software has completed QA and is being published, and will be available this afternoon.The guidance that we have given our users historically is to hold off on upgrading your underlying tooling on the day of the launch until we ship the updates, this release was not the exception and we did post this guidance on March 29th:That said, if you need to use Xcode 9.3 right away, or even on the very date of the release, you can always use the last available builds, the only downside is that they still have labels like "Preview" on them. As of yesterday, all the users on this thread appeared to have sorted the problem out without much complication by switching back to Xcode 9.2.)Hold beta for QA, but definitely don't hold alpha.Just for additional background context, I'll record here that there are a couple complications involved related to that approach.One related complication (though it does not precisely apply to the current scenario) is that publishing to either the Alpha or Beta channel before Xcode 9.3 final was released to the App Store would introduce an error for any users who had not yet updated to Xcode 9.3: "Error MT0091: This version of Xamarin.iOS requires the iOS 11.3 SDK (shipped with Xcode 9.3) when the managed linker is disabled.
0 Comments
Leave a Reply. |
AuthorBrandon ArchivesCategories |