Error initializing the debugger: Mono.Debugging.Soft.DisconnectedException - xamarin.android

After upgrading to version 4.0.4, I started getting the connection with the debugger has been lost error. I've tried to re-install all the components (monodevelop, android sdk, java sdk, etc.). I also cleaned up the registry, rebooted after re-installation. But all the effort did not make any difference. All the android os versions (1.6 to 4.0) targeted all had the same error when debugging. Previous version worked most of the time during debugging. It was quite difficult to find answers on the Xamarin web site. If someone can shed light on this issue, I'd very much appreciate it. Thanks.

I fix the same issue by going to
Mono android options and setting :
linking: adk and user assemblies
Use shared runtime: yes
use fastdeployment: yes
hope that helps

I tried everything rebooting etc.and found this thread during my frustration. At last I tried to build in release mode instead of debug and that magically solved the issue and attached the debugger. There after I could switch back to debug without any troubles.

this problem occurs each time we change a file: for example when you change main.axml file. or when add a new .so file. just run your project twice (first this error appears and for the second turn it run normally)

I encountered this as well.
I upgraded to 4.05 beta, but the problem persisted. Then I disabled the Project Properties -> Mono Android Options -> Use Fast Deployment (debug mode only), selected Deploy Solution manually, and the debugger magically attached and worked correctly.
Not sure if the 4.05 upgrade was needed, but I suspect turning off Fast Deployment was what fixed it.

Restart Visual studio after deleting the .vs,bin and obj folders

I solved this issue by downloading [Mono.Posix.dll][1] and paste it
to path mention in exception. My path : C:\Program Files
(x86)\Microsoft Visual
Studio\2017\Professional\Common7\IDE\Extensions\Xamarin.VisualStudio
[1]https://bugzilla.xamarin.com/attachment.cgi?id=22522
Plus add the following lines in devenev.exe.config at path C:\Program
Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE:
<runtime>
<loadFromRemoteSources enabled="true"/> </runtime>

Run the App in Release mode in not in debug it will work

Related

Debugging symbol file for Plugin.Audiorecorder.dll is not valid and was ignored

When I try to archive my xamarin forms app for publishing it gives the following error: Debugging symbol file for Plugin.Audiorecorder.dll is not valid and was ignored.
When I try to run the app in a simulator everything works fine.
How can I fix this?
I have tried to clean the solution and rebuild it.
I have deleted the bin and the obj folder.
I have changed the debugging options to portable.
But nothing worked
You may have installed other Nuget packages in your app. When archiving it, it'll cause conflicts between assemblies. You should try to resolve it by eliminating those conflicts.
If it still doesn't work, I suggest you directly report it to VS Product Team, from VS > Help > Send Feedback > Report a Problem.

Xamarin building_problem after update to IOS 11

I have updated my system to IOS 11. Visualstidio for Windows with all newest xamarin updates, Mac os Sierra is up to date and Xcode is the newest Version.
My Problem:
If I want to debugging on the simulator, the following error occurs:
Error error HE0046: Failed to install the app 'ch.ABC' on the device 'iOS 11.0 (15A372) - iPhone 6 Plus': lstat of /Users/administrator/Library/Caches/Xamarin/mtbs/builds/ABC/a3481f272dab3f68e6e828203695f442/bin/iPhoneSimulator/Debug/ABC.app failed: No such file or directory
The ABC.app exist in this path on Mac.
Buildlog:
System.IO.FileNotFoundException: The file '/Users/administrator/Library/Caches/Xamarin/mtbs/builds/ABC/a3481f272dab3f68e6e828203695f442/obj/iPhoneSimulator/Debug/build-signature/signature' was not found on the Mac
File name: '/Users/administrator/Library/Caches/Xamarin/mtbs/builds/ABC/a3481f272dab3f68e6e828203695f442/obj/iPhoneSimulator/Debug/build-signature/signature'
at Xamarin.Messaging.Ssh.MessagingFileManager.d__11.MoveNext() in C:\d\lanes\5126\bd7e3753\source\xamarinvs\src\Messaging\Xamarin.Messaging.Ssh\MessagingFileManager.cs:line 171
this signaturefile is also on the right path.
My attempts to fix the error:
-Clean & rebuild has no effect.
-Delete the bin and obj Folder has no effect.
-I made the provisioning completely new has no effect.
-New projects work.
-This project work wehn i build it in Visual studio for mac
Has anyone an idea what could be the problem here?
thanks
Andreas
Edit:
I think that it is a general Xamarin problem. Old projects (before IOS11) can not run after update to IOS 11 in the simulator.
So, I decided to do the whole exercise of step by step mutating a newly created project (which deploys fine to the iOS 11 simulator) into my project (which does not) by using Beyond Compare to change file by file until no difference remains.
That took a good four hours (big project). All of that was to no avail however. :)
Because it turns out that what made the difference in the end was removing the iOS project from the solution and then adding it back (using the "add existing project" command).
This changes three things in the solution file:
Updates it to the latest VS solution format version.
Moves the iOS project to the bottom in a few places.
Fixes up some weird build configuration and/or platform configuration inconsistencies.
Naturally, I thought the last one would be the trick, so I tried only applying that delta in isolation, but that actually didn't fix the issue! I don't fully understand why, but actually performing the action of removing and re-adding the project does.
Very curious to see whether this works for others.

Couldn't get Xamarin projects working with Rider-EAP on OSX

I was really excited, when JetBrains launched the Project Rider-EAP. First thing I've tried was to get a Xamarin-iOS project to run in Rider-EAP, but it doesn't work out of the box.
Update 1: This issue is now listed as critical bug with fix in EAP 2: https://youtrack.jetbrains.com/issue/RIDER-618
1. Problem (fixed) Projects didn't load with the exception that Xamarin.iOS.targets could not be found.
I fixed this with a simple Symlink:
ln -s /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/ “/Applications/Rider EAP.app/Contents/lib/ReSharperHost/macos-x64/mono/lib/mono/xbuild/”
2. Problem
References are not loaded correctly. Therefore the whole syntax highlighting and everything beyond is broken.
See screenshot: References are not loaded correctly
I get the following error as well:
Error:null: Error initializing task MakeDir: Could not load file or assembly '/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Tasks.dll' or one of its dependencies
Switching the xbuild to mono 4.2.2 removes the error but not solves the problem.
PS: It seams that the references are loaded correctly for Xamarin Android projects.
Basic Xamarin Support like open and build is added with EAP 8 of Project Rider.
More advanced features will come with the next Builds and are tracked here: https://youtrack.jetbrains.com/issue/RIDER-1533

Xcode 4.3.2 - One project on two Macs, errors on one, builds on another

UPDATE: QUESTION CLOSED: Fixed myself with a little backtracking. I'm using a framework that requires a source tree variable. (Sparrow). I updated the source tree on my main Mac Mini but not in my MacBook Pro. So, Xcode was searching an old directory due to that mistake.
This may be one of those weird Xcode bugs, so I'm looking for a little advice. I have Xcode 4.3.2 (latest as of this writing Apr 7 2012) installed on two Macs. I have a project saved in Dropbox so I can quickly get at it and work on it from either place. I've done this with several other projects and never experienced this issue.
One one computer, a Mac Mini, the project builds fine. On the other, a 2009 MacBook Pro, I get build errors. For one, even though I'm using -fno-objc-arc on a few of the source files, I am still getting ARC related errors. That is very puzzling to me. No issue when building on the Mac Mini. I'm also getting "file not found" errors pertaining to the .pch file. The error log is pointing me to a strange path like
/var/folders/9l/s_phv6yj0hv6q82_lrdcckb00000gn/C/com.apple.Xcode.501/SharedPrecompiledHeaders/...Prefix.pch' file not found
Here's what I've tried so far
Deleted Xcode and reinstalled from the MAS
Deleted the /var/folders directory called out in the logs
Removed the project build directory
Performed a Product -> Clean in Xcode
Restarted Xcode numerous times
Still no dice. Looks like unless I can nail down this issue, I'll be stuck working from one workstation for this project only. All other projects work fine when doing this.
Thank you for any help you can offer.
I was using a Source Tree variable in XCode, and one of the variables was out of date and pointing to the wrong path. One of the source files that was subsequently updated was working on one Mac but throwing errors on the other, which caused the build to fail and the linker to display strange errors.

Application not getting deployed on Blackberry simulator

I am tried deploying .cod,.alx.jar files on blackberry simulator 8100;the application is not getting deployed on phone.I am using Blackberry plugin for Eclipse.
How can I solve this issue?
Please help
Update
Hi,
Thanks for your reply.
I am trying to run the application the way you suggested.
Do I need to setup new run configuration every time I run any project?
What should be default value for build configuration ? [Debug,Private,or Release]
Copying the .cod files into the simulator's directory (where all the other .cod files are) and restarting the simulator will work.
Probably though you want to automatically deploy from Eclipse. If this isn't working for you, there are a couple of things to check:
Check that the project has been activated for BlackBerry - from the right-click menu for the project, make sure that Activate For BlackBerry is checked.
If that's already checked (as it is by default when you create a new BB project), then sometimes explicitly building the project will do the trick: From the Project menu, choose Build Active BlackBerry Simulation
EDIT: In response to some comments below I thought of something else. The configuration you choose may have something to do with your problems (BlackBerry -> Build Configurations). The configuration in the JDE Plug-in doesn't affect the code generated, but it does affect which projects are activated for BlackBerry. If you switch configurations, your project may become un-activated.
Since it doesn't affect the code, I usually just pick one configuration and stick with it throughout debugging and release.
You might be missing 'jar' in your PATH. If so, the eclipse BB plugin silently fails and your application won't be pushed to your simulator plugin directory. To see this failure within eclipse, choose 'Project > Build Active BlackBerry Simulation'.
If you don't have jar in your path, then you will see:
I/O Error: Cannot run program "jar": CreateProcess error=2, The system cannot find the file specified rapc executed for the project
So, if your JDK is here:
C:\Sun\SDK\jdk\bin
Then append it to your system environment's PATH variable, then re-run 'Build Active BlackBerry Simulation' and you should see:
rapc executed for the project [YOUR PROJECT]
Here are a couple of ideas:
1) If you have any build errors then the application won't deploy to the Simulator. The Eclipse compiler (that underlines compile errors in red) is different to the "rapc" one that creates the binary for the Simulator. I have heard of situations where the Eclipse build seems to work, but the rapc compile fails - check the Console for the detailed rapc output (this might not look like a normal Eclipse build error).
2) In the Eclipse menu, open BlackBerry -> Configure BlackBerry Workspace.
Under BlackBerry JDE choose Code Signing and make sure the three RIM checkboxes are selected. I had compile errors when these weren't selected.
Under BlackBerry JDE choose Installed Components. Choose to use the Component Package 4.7.0 as I have heard of problems with the 4.5.0 Simulator.
You should delete all these extra answers you posted, or you might get downvotes - they should be comments instead of answers.
Check if your simulator is set up to clean the file system / configuration before launching the simulator. Simulators can be set up like this. If you deactivate it, the application should not disappear.
For future readers, there is another possibility for this issue. Check your workbench project directory (folder) for a ProjectName.err file. This may provide a clue as to why your build is silently failing and thus not deploying. In my case, it was an "Error!907", a new icon I added to my project was too big. There was absolutely no other indications in Eclipse 3.4.1 that there was a problem in my build.
Just ran through the same kind of problem : project compiled fine but didn't deploy on any device or on any simulator, even though the debugger said it was attached !
The problem came from a .zip file that was located in the ./src directory of the project, deleting or moving it somewhere else resolved this case.
I wish I hadn't spend 2+ hours on such a stupid problem :/
I know this is old, but you have to do the "generate ALX" option from right clicking the project menu as well or it won't deploy, at least it doesn't for me.
I ran into the same problem again and none of answers posted here worked for me.
I played around and finally made it work. The problem was that the output file name contained a hyphen ('-'). Changing this name in the Build section of BlackBerry app descriptor did the trick.
I mean, how stupid a developer must be to slip that kind of bug. No error reported and why reject the names with hyphens in the first place? Give me back my two hours RIM "developers"!
I had the same problem. The reason was using 'ü' character in the title.
I have been facing this problem today, but with a MIDlet project. It turned out to be that I forgot to specify the "Name of main MIDlet class" in the BlackBerry Application Descriptor (BlackBerry_App_Descriptor.xml). Once I specified it the application appeared on the simulator correctly.

Resources