Subject says it all.
Just upgraded MD to 2.6 and MT to 4.0.7.
Mac OS X 10.6.7, Mono 2.10.1.
MonoDevelop now won't start, just bounces once in the dock and then stops.
~/Library/Logs/MonoDevelop/MonoDevelop.log contains an error:
"GdkPixbuf-Critical: gdk_pixbuf_composite: assertion `dest_x >=
Hi Tom,
I think the new version of MonoTouch requires a higher version of the Mono
framework. You can download Mono 2.10.5 from the website here -
http://www.go-mono.com/mono-downloads/download.html, hopefully this will
resolve this issue.
Hope this helps,
ChrisNTR
On Tue, Sep 13, 2011 at 9:22
Indeed, upgrading Mono to 2.10.5 fixes it. Surprised there's no warning about
this in the upgrade notes visible in MonoDevelop.
Thanks
Tom
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/Just-upgraded-MonoTouch-and-MonoDevelop-MD-now-crashes-on-startup-tp3809441p3809503.h
http://www.fastchicken.co.nz/2010/04/08/monotouch-tableviewcontrollers-and-segmentedcontrol/
On Tue, Sep 13, 2011 at 05:05, ayoung wrote:
> If you're just trying to add the segmented control to the nav bar do this:
> NavigationItem.TitleView.AddSubView(segmentedControl);
> Unless you need to ha
Anyone know how to do this properly?
I need to reinstall clean, to try to fix a different problem. (
http://bugzilla.xamarin.com/show_bug.cgi?id=709 )
--
Nic Wise
t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
b. http://www.fastchicken.co.nz/
mobileAgent (for FreeAge
On 13.09.2011 10:52, tomf84 wrote:
> Indeed, upgrading Mono to 2.10.5 fixes it. Surprised there's no warning about
> this in the upgrade notes visible in MonoDevelop.
Actually, I've got an error message about the missing Mono 2.10.5
but it showed up only after I've restarted MonoDevelop 2.6 twice.
This is happening AGAIN! arrgh!
This time the error code is slightly different.
AMDeviceInstallApplication returned: 0xe8003ffe
Tried it on iPad 1, 2x iPhone 4's and an iPhone 3GS. Same problem on all of
them. It happened out of no where. Last thing I remember changing was the
name of a key in m
And just as before, doing a restore of the changed file, or even a full
restore of my project folder from a Time Machine backup still makes no
difference. Changing to a different device doesn't either.
There is something, somewhere in the configuration files of
mono/develop/touch that has chan
On 13.09.2011 10:59, Nic Wise wrote:
> Anyone know how to do this properly?
>
> I need to reinstall clean, to try to fix a different problem. (
> http://bugzilla.xamarin.com/show_bug.cgi?id=709 )
sudo rm -rf /Developer/MonoTouch
Robert
___
MonoTouch ma
sudo rm -rf /Developer/MonoTouch
and check, double check and triple check. You wouldn't want to create a D'Oh
moment :-)
D
David Black
Technical Manager (Web projects)
Casewise Systems Ltd | www.casewise.com
+44 1923 830300 office
+44 1923 830270 direct
64 Clarendon Road, Watford WD17 1DA
Ok, I feel a little stupid. It turns out my key UIApplicationModes had a
space in front of it. Doh!
Well, to anyone having similar problems, ensure your info.plist looks like
this
UIBackgroundModes
audio
and setup your playback code like this:
AVAudioSession audio
I'm pretty sure I'd still have cached help files in other places,
which is exactly my problem (and that also doesn't remove the
license,which is in ~/Library)
But I'll give it a try.
On Tue, Sep 13, 2011 at 11:41, David Black wrote:
>
> sudo rm -rf /Developer/MonoTouch
>
> and check, double
A different error code means a different reason why the device refused
to let you install your application.
Anyway the same drill (as before) still applies. We need a bug report,
a test case and the logs to duplicate the issue. Without them we
cannot fix or, at least, provide a more useful error m
Following on from this morning's upgrade to MT 4.0.7, I am now finding mtouch
is crashing on code which worked fine yesterday, when compiling in Release
mode only.
Error 1: mtouch failed with the following message:
Unhandled Exception: System.NullReferenceException: Object reference not set
to an
Dermotos,
As Sebastien says, this issue is the device refusing to let you install the
application. It might be worth checking "Settings -> General ->
Restrictions" and making sure that "Installing Apps" is set to "On".
Hope this helps,
ChrisNTR
On Tue, Sep 13, 2011 at 1:27 PM, Sebastien Pouliot
Hello Tom,
This affects a few* projects when building for devices only (simulator
builds are fine). MonoTouch 4.2 ('beta' now,but should be moved to
'stable' soon) already has the fix for this. More details in:
http://bugzilla.xamarin.com/show_bug.cgi?id=604
Regards,
Sebastien
* no one could pro
Hi Tom,
I don't think it's that MonoDevelop necessarily *requires* Mono 2.10.5, it's
just that 2.10.5 ships a newer version of Gtk+ which has presumably fixed
the bug that you were seeing.
Jeff
On Tue, Sep 13, 2011 at 4:52 AM, tomf84 wrote:
> Indeed, upgrading Mono to 2.10.5 fixes it. Surprise
I've always been kind of baffled that Apple doesn't include any native UI
for doing expand/contract (or show/hide) controls. This seems like a
natural fit for a touch device
so I'd also really love to see a good example of how to accomplish this
On Mon, Sep 12, 2011 at 10:44 PM, bamagrad03 wrot
Hi Nic,
You shouldn't need to remove the ~/Library/MonoTouch/License.v2 file (I'd
recommend not removing it, in fact ;-)
The only way I know of to uninstall MonoTouch (and I'm kinda new to MacOSX,
so there might be a better/cleaner way... but)
sudo rm -rf /Developer/MonoTouch
sudo pkgutil --forg
Thanks Jeff
I'll give it a go when I get home. Hopefully, that'll fix my
intellisense problem and means I can do some work.
On Tue, Sep 13, 2011 at 15:44, Jeff Stedfast wrote:
> Hi Nic,
> You shouldn't need to remove the ~/Library/MonoTouch/License.v2 file (I'd
> recommend not removing it, i
I had the same issue and rolled back to 4.0.4 and that solved the problem for
now. So If you can downgrade it might be worth trying
D
David Black
Technical Manager (Web projects)
Casewise Systems Ltd | www.casewise.com
+44 1923 830300 office
+44 1923 830270 direct
64 Clarendon Road, Watford
Can we get someone on the MT team to speak to this? I'm seeing the same issue
and its pretty bad.
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/MonoDevelop-2-6-MT4-2-unusable-tp3803633p3811230.html
Sent from the MonoTouch mailing list archive at Nabble.com.
_
Hi Andrew,
We've got a bug open on this on Bugzilla here -
http://bugzilla.xamarin.com/show_bug.cgi?id=709
If you could give your feedback on the issue then that would be great.
ChrisNTR
On Tue, Sep 13, 2011 at 10:18 PM, ayoung wrote:
> Can we get someone on the MT team to speak to this? I'm
Thanks for the replies.
Unfortunately as it's a show-stopper I needed to implement my work-around
(recreate the project as a new project), but next time it happens I will
make a copy to continue working, so I can submit a bug report and be able to
continue providing you with information from the br
Intellisense on 2.8b1 doesn't seem to be working correctly. Forgive me if
I'm being stupid - I'm new to MonoTouch. But even on the simple AppDelegate
it won't allow me to reference window inside the FinishedLaunching()
function.
It's clearly defined. Even a new variable that was defined immedia
Hi James,
You are correct, there is currently a bug in 2.8b1 that causes
this behaviour. This has been fixed (you can see the bug report here
http://bugzilla.xamarin.com/show_bug.cgi?id=734) and will be in the next
version of the MonoDevelop 2.8 betas.
Hope this helps,
ChrisNTR
On Wed, Sep 14,
Yes, MonoDevelop 2.8beta1's intellisense is horribly broken. We'll be
putting out beta2 shortly which should fix that.
Jeff
On Sep 13, 2011 8:07 PM, "netboy2005" wrote:
> Intellisense on 2.8b1 doesn't seem to be working correctly. Forgive me if
> I'm being stupid - I'm new to MonoTouch. But even
I appear to have a corrupt MonoTouch-lib.zip (mentioned at the bottom
of the bug). The unzip from Mike didn't work - zip was corrupt.
Not sure how to fix, other than get a working one, or delete it.
On Tue, Sep 13, 2011 at 22:34, ChrisNTR wrote:
> Hi Andrew,
> We've got a bug open on this on Bug
28 matches
Mail list logo
