My UWP Xamarin.Forms works fine in Debug mode, but crashes in release. This is MenuPage.xaml.g.cs:
Added
I was able to get deeper, please see
FreshPageModelResolver.ResolvePageModel() throws an exception in UWP Release
What could be the cause of this?
It could have something to do with your linker options - for Release "Link Framework SDK's only" is often selected, while "Don't link" is selected for Debug.
Try setting "Don't link" for your Release config and see if that is the issue - if yes, you need to figure out what is being linked which it shouldn't, and include it.
Hope it helps :)
Related
I can debug my app just fine. Everything works. As soon as I set it to release, the app doesnt start. It just crashes on startup with no explaination. Setting the linker to "link assemblys and sdk" the app starts but with major bugs (texts missing, classes not loading)...
Same happens when the linker is active and the app is in debug mode.
I can only start the app in debug mode with linker set to none.
However, without alterting anything, yesterday it worked for a few builds. I could start the app in release.
Today it stopped working again.
I am completely out of ideas. The picture below is my android set up for release.
Why cant I start with no linker ? Build works fine...
*** EDIT:
I also just relised, i cannot start ANY project in releas with linker set to none. Even when I start up a new projekt from xamarin.forms, the first build in release already fails
So, it turns out that VS has to be start as administrator if I wanna start a release build. That was never the case... But it fixes it ...
Try to start my project on one iOS8 simulator and Xcode shows error:
An error was encountered while running (Domain = NSMachErrorDomain, Code = 5)
No one of iOS8 simulator can't be started. What to do?
"iOS Simulator" -> "Reset Content And Settings..."
^ this helps.
I ran into the same error just this morning, and I haven't completely figured it out, but I have observed something which might help you (or both of us, if anyone else stumbles across this and has more information). I was building a project which contained:
the app itself
a Today extension (widget)
a Framework to share code between the app and the widget
The widget comes with TodayViewController.h/m, and I wanted to share this view controller with the app. So I changed the target membership of TodayViewController.m to my framework rather than the widget. (Did this in the Target Membership in the right sidebar.) I also set the TodayViewController.h to be part of the framework as a public header. When I did this, and then did a clean, I got this error when trying to run the app in the simulator, and also an "unknown error (null)" when trying to run on device. If I set TodayViewController.m's target membership to both the framework and the widget, I'm able to run the app in the simulator just fine.
Now, I don't know why this would be the case. I've declared my widget to depend on the framework, so it seems like it should work without my setting the target membership of TodayViewController.m to both widget and framework. If anyone else knows why this is the case, I'm all ears. But this is what I've found so far.
I had the same problem tonight too. I was not able to get my app to run if my resource directory was a "folder reference" (aka blue folder). Once I re-added my resource directory as a "folder group" (normal folder) instead my app ran fine. Not sure if this is the case for you, but it solved my problem. GL.
I ran into the same problem today using DP3.
When I tried to delete the Derived Data folder from Organizer, it showed me some kind of permission error. I then manually deleted the folder from Finder, rebuilt, and voila! It worked!
If you ever get and error like this, where xcode doesn't say much, just a error code, try first to check the actual problem on the system console.
Applications -> Utilities -> Console
On my case I was able to see that xcode was trying to copy the widget's binary and it was not able to find it. I was able to find out that without at least one compiled file on the extension's target, xcode is not going to create the binary for the extension.
We develop a Silverlight application, the latest version of which we have just deployed to our clients.
The problem is that some of our clients are getting errors when they attempt to access the application in Internet Explorer. The application loads fine in Google Chrome.
The error initially manifested itself as showing the Silverlight loading animation, getting to 100% and disappearing leaving a white page or simply sticking at 100%.
Having enabled JavaScript debugging, an error dialog appears informing the user of the following:
Line: 62
Error: Unhandled Error in Silverlight Application
Code: 2110
Category: InitializeError
Message: 2110 An error has occurred.
We cannot get any further than this. Can anyone shed any light on this issue?
Thanks very much,
Martyn.
I am very late, but since I could not find the answer that eventually solve the issue for me I am posting here for others :
In my case, the answer was to set back the compilation platform to "any CPU" I got the 2110 error in x86 and it loaded properly using "any CPU".
In my experience this is almost always a problem with dependencies.
To prove that it is, create a new Silverlight project and include all the references you have in your existing project and see if you get a white screen of death.
If you do then try removing references from your test SL project one at a time until you get something that works.
HTH
There are many reasons that cause this error. It may be from your code or IE itself. Could you ask the users do things such as:
Try to disable IE9 compatibility view. (Press F12)
Clear IE cache then close and re-open it before you go to the website.
If none of them works, you should check xaml code or attach the Silverlight process to the debugger and debug the code.
I have the same problem, but in Firefox x64, when I have in Silverlight csproj:
<Reference Include="mscorlib">
<Private>True</Private>
</Reference>
When I changed it to:
<Reference Include="mscorlib" />
everything goes well.
This is the message while trying to run under XCode 4 (it used to work under XCode 3):
No provisioned iOS devices are available. Connect an iOS device or choose an iOS simulator as the destination.
I have profiles for my device for this app... where should I be looking to correct this?
The problem is that your iOS Deployment Target in Project-> Build Settings is different from the current version of iOS on your real device.
You're asking where to find it:
In XCode 4 there is a new button - look for the big
"Organizer button"
which is at the TOP RIGHT.
Physically connect your device and then click Devices. It seems that the new "Organizer button" is one of the "most-missed" things in the transition to XCode4.
Note, the questioner is asking: "WHERE should I be looking to correct this?"
I was having extra trouble because of my Enterprise License, but still updated the iPads. I didn't have to change anything in the Build Settings to lower. But the main thing that I had a problem with was in the Organizer I needed to hit "Use for Development" button.
Kind of an old post, and may not be the best way or a rookie thing to miss but wanted to help anyone out.
My problem similar to those above were related to having the deployment target set too high for the version installed on the phone. Would be nice if it gave a more useful error message. I spent hours messing with my provisioning profile trying to fix it, when the real problem was the older version of the software on the phone.
I had the same problem. The reason was simply, that my ipad had not been update to version 4.3.
This just happened to me for iOS5 with xcode 4.2.
The answer is to go into organiser, select your device, and press the "Develop with this device" button (or similar wording).
Then go back and build, and it should work..
I received this error while having an iPad properly connected.
Some info:
Ipad iOS version: 4.2.1
XCode 4.2
XCode project created with "iOS Application / Empty Application" template.
The problem was that I had to specify the "iOS Deployment Target" to 4.2 in more than one place!
That is, both in the "Build Settings" and in the "Summary".
Very odd, and definitely another XCode4 annoyance.
I got this error in Organizer - "Could not support development.". I tried rebooting the iOS device and it worked for me :)
Check that the Executable File (also known as CFBundleExecutable) in the Info.plist file is set to ${EXECUTABLE_NAME} as opposed to any hardcoded value. This will ensure that even if you change your project name or target name or scheme name, that it still works.
you need to install the proper version of iOS.in my case it is iOS 4.0 - 4.1 Device Debugging Support
GOTO --> XCode Preferences -> Downloads --> Component
there are all updates available for your iOS click Install.
This is works for me.
It looks like this error can also come about if the "Product Name" in your target's build settings does not match the value of "CFBundleExecutable" in your info.plist
It looks like to me this is the general error Apple gives if the executable is not installed correctly on the device. When the debugger tries to attach it looks for the executable name and if it's not there they give this error. Touch one to debug.
Go to build option and select valid compiler.
Chose your right iOS Deployment version
in my project when i build the project it is giving this message :
To debug this module, change its project build configuration to debug mode. To suppress this message, disable the "Warn inf no user code on launch" debugger option
due to this when i place the break point. break point is not working. can u help me.
Check that the Standard toolbar shows that you are working in Debug mode. This is the most common cause for this problem. This setting controls what mode the Run will use. (Too see this toolbar, right click in the Visual Studio menu area and make sure the 'Standard' toolbar is checked.)
Check that you are not running with ctrl+f5 (which equals Start Without Debugging). This does not match the error message you get, so likely not the answer.
Check that the Solution Configuration does not specify that the project should be built in Release mode. To access this, right click the solution, see properties for the solution and then review the configuration settings for your projects in the configuration dialog editor that pops up.
you're trying to debug your project in Release mode... Switch the project into Debug mode, click Rebuild and then press F5.