- #Reason 10.3 update not working anymore apk#
- #Reason 10.3 update not working anymore update#
- #Reason 10.3 update not working anymore code#
- #Reason 10.3 update not working anymore mac#
Do you have any spaces or punctuation characters in yours? I've found that the name of the folder that contains your project can make a difference. I also noticed that "Bundle assemblies into native code" got checked somehow, but disabling this only helped part of the problem which was to go from hitting no breakpoints to hitting misaligned breakpoints.
#Reason 10.3 update not working anymore apk#
I had not upgraded Xamarin in at least 2 months but I had just upgraded my Android SDK tools/libraries (not changing my targets), went from Debug to Release back to Debug builds in my project, and turned on "Use Shared Runtime" to create an APK for my client, but then I turned it back off.
#Reason 10.3 update not working anymore code#
I still have the age-old issue of breaking on some code outside of my project which can't be disassembled or which has no debug info, but hitting "Continue" or F5 brings you to the correct breakpoint. SOLUTION: I upgraded to the latest Alpha channel (Xamarin 3.11.785 which contains Android v5.1.5) and it solved my debugging issues. However, Tim's answer above led me to the right solution. Nothing above worked-not even deleting all obj and bin folders, clearing all breakpoints, or deleting my. When I say "misaligned", I'm talking about hitting breaking on classes I'm not even referencing. I was having similar issues with missed or misaligned breakpoints in my Android project running from VS 2013-particularly inside async tasks. But I'm sure the Xamarin team will get it working again!Īh yes, I also wanted to mention that I do NOT have any Xamarin.Forms stuff installed.this is strictly Xamarin.Android. Unfortunately, I cannot re-enable the "Use Shared Mono runtime" as it won't allow my app to start anymore, which is too bad because now deployment takes at least twice as long. This is a summary of narrowing down the most recent steps that seemed to work. This time breakpoints were working again! I then re-enabled the developer instrumentation, uninstalled the app from the device, and redeployed again. Then I cleaned, deleted bin/obj folders, rebuilt, and redeployed and no breakpoints were hit (expected because of the disabled instrumentation I think). I also uninstalled the app from the device itself (not using an emulator) via Google Play Store > Uninstall. What finally worked for me was going to the solution options, unchecking "Use Shared Mono runtime" and "Enable developer instrumentation.". User68480 I feel your pain, and I'm not sure if this applies to you, but I've finally gotten it working on Xamarin.Android.
#Reason 10.3 update not working anymore mac#
I've seen a couple of posts that say rebooting my mac may fix it.
#Reason 10.3 update not working anymore update#
I've checked that it's being recreated every time by checking the build log (it is).Īll sorts of stuff seems to have broken since yesterday's update to xamarin ios 10, monotouch, etc. However, as soon as I delete the app from the emulator and redeploy, it reappears immediately. It's like it's not getting updated on the emulator, even after a clean and rebuild. XxxiOS warning: Symbol file /Users/johnw/Library/Developer/CoreSimulator/Devices/316F5DE3-0617-402B-AFC8-933452456F42/data/Containers/Bundle/Application/E2218027-0EFF-4EE4-9BAE-A30F0A363A5C/xxxiOS.app/.monotouch-32/.dll.mdb doesn't match image (null) Additionally I have started seeing this message appear in the debugging output: I've got exactly the same problem (among others).
0 kommentar(er)
