Hi everyone,i've just using gideros and it's really nice. I just wanna ask, if gideros support for android only for android 2.2 (froyo) and 2.3 (gingerbread) version? Because when I try it on ICS and jelly bean (ICS real device and emulator,jelly bean emulator),the application won't run and just stopped. When i try it on froyo and gingerbread,it run well,using both real device and emulator. The logcat show the eror below
10-23 07:58:42.830: E/AndroidRuntime(1618): FATAL EXCEPTION: main
10-23 07:58:42.830: E/AndroidRuntime(1618): java.lang.ExceptionInInitializerError
10-23 07:58:42.830: E/AndroidRuntime(1618): at java.lang.Class.newInstanceImpl(Native Method)
10-23 07:58:42.830: E/AndroidRuntime(1618): at java.lang.Class.newInstance(Class.java:1319)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.app.Instrumentation.newActivity(Instrumentation.java:1023)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1871)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1981)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.app.ActivityThread.access$600(ActivityThread.java:123)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1147)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.os.Handler.dispatchMessage(Handler.java:99)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.os.Looper.loop(Looper.java:137)
10-23 07:58:42.830: E/AndroidRuntime(1618): at android.app.ActivityThread.main(ActivityThread.java:4424)
10-23 07:58:42.830: E/AndroidRuntime(1618): at java.lang.reflect.Method.invokeNative(Native Method)
10-23 07:58:42.830: E/AndroidRuntime(1618): at java.lang.reflect.Method.invoke(Method.java:511)
10-23 07:58:42.830: E/AndroidRuntime(1618): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
10-23 07:58:42.830: E/AndroidRuntime(1618): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
10-23 07:58:42.830: E/AndroidRuntime(1618): at dalvik.system.NativeStart.main(Native Method)
10-23 07:58:42.830: E/AndroidRuntime(1618): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load gideros: findLibrary returned null
10-23 07:58:42.830: E/AndroidRuntime(1618): at java.lang.Runtime.loadLibrary(Runtime.java:365)
10-23 07:58:42.830: E/AndroidRuntime(1618): at java.lang.System.loadLibrary(System.java:535)
10-23 07:58:42.830: E/AndroidRuntime(1618): at com.giderosmobile.android.SewersActivity.(SewersActivity.java:22)
10-23 07:58:42.830: E/AndroidRuntime(1618): ... 15 more
So,any ideas how to solve the problem? Looking for your help guys,thanks.
Comments
It appears that findLibrary couldn't load libgideros.so from the libs/armeabi or libs\armeabi-v7a folders.
This would suggest that maybe these folders are missing and that's where your problem lies. This can sometimes occur if you are writing your own plugins and have cleaned the project. I found that eclipse will delete the folders if you try to clean the project when writing/using your own plugins.
The way I get around this is by copying the libs folder to another folder (usually lib) and modify my Android.mk file to use this folder instead like so
Website: http://www.castlegateinteractive.com
https://play.google.com/store/apps/developer?id=Castlegate+Interactive
https://github.com/gideros/gideros
https://www.youtube.com/c/JohnBlackburn1975
Just kidding.
@john26 you see the problem is it would produce even more problems. In eclipse you can debug app to find if there is any different from Gideros player (usual problem - case sensitive filenames).
It would require @atilim to invest a time in such a feature.
I actually do not know if this is even possible.
Likes: KeepTrying
The only way Gideros Studio could totally remove the need to use Eclipse would be to incorporate the ability to run Ant scripts (or some other scripting system) to do the java compilation & signing within the Gideros Studio IDE and I'm fairly confident that this is not going to happen any time soon (if ever).
I have to confess that I can't see any problem with loading a project into eclipse and exporting the release APK. It takes a couple of mouse clicks and requires very little interaction with eclipse except to select the appropriate key with which to sign your app.
Doh!! Ninja'd
Website: http://www.castlegateinteractive.com
https://play.google.com/store/apps/developer?id=Castlegate+Interactive
@Scouser, actually I was particularly worried about what you said:
"I found that eclipse will delete the folders if you try to clean the project when writing/using your own plugins"
It horrifies me to think Eclipse will delete random stuff from my project! That's one reason I'd like to avoid this beast.
It seems to me to avoid needing Eclipse, Gideros would only have to emit a build.xml file. We could then compile using Apache ant (which comes bundled with Android or Eclipse, I forget which)
https://github.com/gideros/gideros
https://www.youtube.com/c/JohnBlackburn1975
Here in this tutorial:
http://appcodingeasy.com/Gideros-Mobile/Creating-plugins-for-Android-in-Gideros
I describe a way to generate new or copy existing libs when building and testing plugins using Android.mk file