Object Disposed Exception #1194
Comments
|
I'm seeing similar strangeness in #1196. I just found this because I also get |
|
In this particular case, it was not repeatable. I just ran my exact same script again and this time it worked. However, there are still a heap of asian characters in the output. Also, #1196 seems to "fail" every time. |
|
When I start IOS hockey my script failed with this exception, but when I open a new tab in ITerm2 , everything start to build properly, but than appear again. |
|
Hello guys , still got this error. Any ideas ? |
|
Still getting this with 4.28.0 :( |
|
Same here :( |
|
It's very important bug , that stopped our CI for a while. |
|
any ideas what to do? |
|
I do have Xamarin support looking into this and other issues. Basically I gave them my whole project and said here, this should build on both mono and Windows but doesn't on either. They have confirmed issues and said they'd get back to me. Will update this thread when they do. |
|
Thanks for the update kentcb ! You have a temporary workaround available ? Since this is breaking our CI environment as well. |
|
Same problem. seems intermittent |
|
Same issue - causing us serious issues :-( |
|
// cc @nosami |
|
Any idea on where to look for a certain solution ? Did you guys do a rollback of mono ? Since rollback of FAKE does not fix this issue. |
|
As a workaround till the issue is fixed, updated TeamCity to invoke the following This is used only for Android Package target from CI tool, so the exception is ignored and the build does not fail. |
|
whereabouts do you put that line? in the fake script? we have already set TC to ignore all errors for the moment. Seem to get the Chinese characters intermittently on a number of different build steps atm. seems to be when a shell command is run? |
|
we also get the hockey app problem, although it seems to succeed despite the odd characters |
|
@ewan-fraedom the code is not part of the fake script. This is a regular shell script that invokes the Fake script (build.fsx file) and ignores the object disposed exception. You can save the script in a android-package.sh file and invoke the script as follows - |
|
gotcha |
|
Also experiencing this on a similar setup - TeamCity, Xamarin, OS X for an Android build. I've tried a few alternative approaches to the trapping suggested by @bgidwani, but nothing seems to reliably prevent the error. For now I'm just going to build on Windows (which so far seems to not fail, or at least fail a lot less). I'd greatly appreciate a workaround that preserves logs, and will be happy to provide more information or help with testing any possible fixes. |
|
Got these crashes after upgrading to the cycle 7 Xamarin. Sometimes build works fine, sometimes I see object disposed. After compiling Android. Though I do not get any Chinese characters. |
|
Which version of the zipAlign tool are you using when executing the AndroidSignAndAlign ? |
|
~/Library/Developer/Xamarin/android-sdk-macosx/build-tools/23.0.1/zipalign Is there a way to debug this exception to find out which file and who's trying to access? |
|
Hey guys, just catched something very unusual in the build log Here you can see that aligner is still verifying the apk while the code after validation is already executing in F#! This is the code What am I doing wrong? |
|
Here is what I did to get rid of the problem. To test my strategy I basically made a copy of If you see the output from previous message, the log had like 20 messages from zipalign but in reality there are almost 500 lines in the output from zipalign that were never displayed (even in the old builds which did not fail and run on the mono 4.2 before Xamarin cycle 7 update). My guess is that it's related to the garbage collection changes but who knows. I'll test the changes for a few days and will make a PR. Appreciate any feedback or comments |
|
Awesome. Please send pr
|
|
@alexsorokoletov thanks for the update ! With version .29 we are getting this exception :
|
|
also in AndroidPackage [android-package] /Library/Frameworks/Mono.framework/Commands/mono "tools/xpkg/xamarin-component.exe" restore ../TravelApp.sln |
|
Is it happening only with 4.29? |
|
Can reproduce, will be fixing the problem Alex
|
|
hmm ok so 4.28 [10:31:10][android-package] Starting Target: android-package 4.29 [android-package] Starting Target: android-package |
|
Problem identified, checking the fix and will provide a fresh pull request soon |
Undo all changes in ProcessHelper made for #1194
|
still getting some enconding issues with 4.29.2 [12:03:31][core-build] Build property string |
|
@ewan-fraedom I had to rollback encoding fixes in all processes cause this turned out to be much more complex issue that should be addressed. |
|
An update to 4.29.2 did the trick for me. I also noticed that the output directory of the .ipa changed, so I had to make some adjustments in my configuration here as well. But at least it works now with the latest Mono bits again. |
|
yeah the output directory change is v annoying. is it fake related though? we tried to fix by specifiing outputdir and/or outputpath but found that it incorrectly appends the filename to the last directory. ie outputdir = ./bin/iPhone -> ./bin/IphoneMyApp.ipa when really you want ./bin/iPhone/MyApp.ipa |
|
That's a mess I gave up on ;-). What happens with the iOS helper: Given that configuration I would expect to find everything within |
|
yeah best i can tell is that its not using the default output path of the bin dir and then MSBuild or whatever is doing its default 'no output path' behaviour then if you specify the output path there is a bug where it treats the last dir as something to prepend to the filename. tried all variations of ./directory/./ etc |
|
Yep, and so did I. I am suffering a little OCD here knowing files are thrown in directories where they do not belong, but as I don't have to watch it while it's running on the build agent, I can live with that. It's just a bit annoying to figure out how things (not) work. (But my F# knowledge is to limited at this point to dig deeper and provide a fix.) |
There is a bug for that in Xamarin http://stackoverflow.com/questions/37726925/xamarin-cycle-7-ios-ipa-output-now-in-a-datetime-folder/ |
|
I think those are two different things. The one thing is that folder with the timestamp, the other, storing everything outside the configured target directory, is more likely to be FAKE/XamarinHelper related. It ends in |
|
The IPA output path change is a separate issue that I have also been hounding Xam support about. It's apparently been fixed, but not released yet. See https://bugzilla.xamarin.com/show_bug.cgi?id=41963 for discussion and possible interim workarounds. smh at how this got through to stable. |
See fsprojects/FAKE#1196, fsprojects/FAKE#1212, fsprojects/FAKE#1213 & fsprojects/FAKE#1194 Not sure of the ramifications of this change, but this fixes the encoding issues in FAKE for me. l.Head.Encoding was `System.IO.StringWriter(new System.Text.StringBuilder()).Encoding` which evaluates to utf-16 /cc:@forki
After some time my CI start to raise unhandled Object Disposed exception. IOS works fine, problem in android.
After in build it try to create "Signed" apk.
And after FAKE do some target I get some chinese symbols
FAKE version 4.22.9
Mac OS X El Capitan v. 10.11.3
Zipalign r. 23.0.2
Update 1 april 2016:
Now ios stop building too.
What it can be ?
The text was updated successfully, but these errors were encountered: