Xamarin iOS crashes in debug randomly with error described. #5267
Comments
VincentDondain
added
iOS
|
Any fix to this or idea about what I should do because I am stuck I cannot continue developing app and the error does not tell me anything immediately useful about what could be wrong so i can solve it... |
|
@RazvanEmilR the error is not clear but
strongly hints it's related to XVS and the bug has been assigned to this team for investigation. In the meantime I suggest you try to debug directly from the Mac (using Visual Studio for Mac) since that error should not happen locally. |
|
@spouliot Thanks so much for the tip, and for forwarding the bug. I was really stuck doing my work. Will try using Visual Studio for Mac. |
|
@spouliot Im getting same error when I run the project on my Macbook as well. I just don't understand if its from my code or its a bug in Visual Studio. What I know is that im at the third version of the app and I never modified the code on the page on which the error appears when its just quits with the error message above, and it worked fine until now. On top of that this error never appears in the simulator.... So that means it cant be from my code? What resource is missing? Any other ideas? |
|
Hi @RazvanEmilR, Could you please Gist us your full verbose logs (build + application output + any crash you get) when running on the Mac and also on Windows (again, since I don't think your logs are complete)? The error Sebastien referenced #5267 (comment) IDB412377 should definitely not happen with VSMac, it's Windows specific. In addition if you can provide a small test project so we can try to reproduce locally that would be helpful (: |
|
@VincentDondain @spouliot |
|
Sorry we can only help with Xamarin.iOS issues, we're not Azure experts in this particular team (: |
|
@VincentDondain I understand. I just got this idea now about what could be the problem. I am not sure if it is so, but it sounds plausible to me. I will explore further and confirm. |
|
@RazvanEmilR I'm closing the issue since there has not been any updates for a long time. Please feel free to open the issue if you consider this wrong. |
ghost
locked as resolved and limited conversation to collaborators
Steps to Reproduce
Expected Behavior
After last break point, visual studio waits for further action with the app still running in debug mode.
If running the app on device disconnected from computer it will not crash.
Actual Behavior
App crashes at random times with the error below.
App on device also crashes when running disconnected from computer.
Note: App runs fine in simulator without crashing.
App ran fine in debug before, no code changes made to the respective pages.
Thread started: #11
<title>The resource cannot be found.</title> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }Thread started: #12
2018-12-12 11:33:40.016 MyApp.iOS[1201:234792] Token received: <c888863b cb362ba8 3028fa09 ea6171ce e88231e3 f1d5f6a3 071e47aa 1b2511e3>
Thread started: #13
Thread started: #14
Thread started: #15
Thread started: #16
2018-12-12 11:33:42.934 MyApp.iOS[1201:234792]
@media screen and (max-width: 639px) {
pre { width: 440px; overflow: auto; white-space: pre-wrap; word-wrap: break-word; }
}
@media screen and (max-width: 479px) {
pre { width: 280px; }
}
</style>
nformation: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3163.0
Environment
Build Logs
Example Project (If Possible)
The text was updated successfully, but these errors were encountered: