Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 533 [details]
since today, when i change things on my Project in IF Builder (change color of uIbutton), it seems to be saved,...
i close the if builder, reopen it, after building the project and running it, the change is away again,..
if i add a new button to the Bedienteil.xib and i save it and then build and reopen Xib, button is away again,...
It is actually happening , with actual version!
I tested it on 2 Macs with same solutions
Mac OS Lion btw :-)
also other changes, like repositioning, the button and saving it, has no effect....
if i add a button, i call the button "asdf" in the if builder (drag and drop -->outlet), i see the button in monotouch afterwards and can use it , but after compiling during running, "asdf" ithrows null reference exception because "asdf" is null, when i use it,.... even in viewdidload (there the button already should exists,,,,,and after that ....
do you need video?
Heh, that comment was supposed to be internal to the team just to point out that this is a pretty important issue, I wasn't doubting you, I just hadn't attempted to replicate the issue yet. I'm looking into it now anyway!
The cause of this was because Bedienteil.xib had a modification date which was a month or two into the future. This broke our logic for deciding if the file we gave to Xcode has been modified. The date in the future basically meant that MonoDevelop thought the file had not been changed and so it was never synced.
To work around the issue for now, just modify all your files in some form in a text editor (i.e. monodevelop) and save them to give them a proper modification time. The fix will be in 2.8 final.
ok, :-) your comment is ok, you do very goood work :-)
so the reason is, the modificationdate, so if on one mac there is a wrong modification date, and it saves the things...
what do i have to change with texteditor? i am not used to this...
another idea for workarround:
set my year to 2012?
All you have to do is open any file that is not syncing properly, make a modification to it and hit 'save'. Simplest thing to do is right click on your xibs, open with the text editor, add a space, hit save, remove the space, hit save.
ok thx :)
have a nice weekend!
I should also mention that you should probably do this from within monodevelop, don't do it from inside Xcode as that won't help :)
this was fixed a while ago