Quantcast
Channel: Recent Threads — Xamarin Community Forums
Viewing all articles
Browse latest Browse all 204402

OpenTK crashes after upgrade to latest Xamarin.iOS in ad-hoc distribution

$
0
0

(Creating a new thread since the title from previous post wasn't clear. http://forums.xamarin.com/discussion/6392/unhandled-managed-exception-libgles-dll-system-dllnotfoundexception)

When building an OpenGL iOS App after upgrading to the latest Xamarin build, it crashes only when I build a signed, distribution archive of the app with the following error:

Unhandled managed exception: libGLES.dll (System.DllNotFoundException) at (wrapper managed-to-native) OpenTK.Graphics.ES11.GL/Core:GetIntegerv (OpenTK.Graphics.ES11.All,int*) at OpenTK.Graphics.ES11.GL.GetInteger (All pname, System.Int32& params) [0x00000] in :0 at OpenTK.Platform.iPhoneOS.GLCalls.m__8 (All n, System.Int32& v) [0x00000] in :0 at OpenTK.Platform.iPhoneOS.iPhoneOSGameView.CreateFrameBuffer () [0x00000] in :0 at OpenTK.Platform.iPhoneOS.iPhoneOSGameView.Run (Double updatesPerSecond) [0x00000] in :0 at OpenGLESSampleGameView.OpenGLESSampleAppDelegate.FinishedLaunching (MonoTouch.UIKit.UIApplication app, MonoTouch.Foundation.NSDictionary options) [0x00000] in :0 at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication:UIApplicationMain (int,string[],intptr,intptr) at MonoTouch.UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) [0x00000] in :0 at MonoTouch.UIKit.UIApplication.Main (System.String[] args) [0x00000] in :0 at OpenGLESSampleGameView.Application.Main (System.String[] args) [0x00000] in :0

It appears to be a problem with OpenTK because I've tried all sorts of different configurations and have reproduced this on both my app and the OpenGLES sample on xamarin/monotouch-samples (https://github.com/xamarin/monotouch-samples/tree/master/OpenGLESSample-GameView). This is making it impossible for us to send out a working build on TestFlight so I am hoping that someone might have run into this as well and know of a workaround or fix... Is there a way to revert back to a previous version of Xamarin.iOS perhaps?

UPDATE: This might be the same or related bug. https://bugzilla.xamarin.com/show_bug.cgi?id=13498

Thanks in advance!


Viewing all articles
Browse latest Browse all 204402

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>