mirah / pindah

Tools for building Android applications with Mirah
Apache License 2.0
228 stars 27 forks source link

Basic project crashes on launch #44

Closed JJJollyjim closed 10 years ago

JJJollyjim commented 10 years ago

I've set up a simple project with a single activity. It crashes as soon as it launches with a RuntimeException. I get the same error in any sample projects I can find online. Versions of things:

$ ruby --version
  jruby 1.6.8 (ruby-1.8.7-p357) (2012-09-18 1772b40) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_65) [darwin-x86_64-java]
$ mirah --version
  Mirah v0.1.1
pindah: just installed today from git
android: 4.3 on flo

I noticed when trying to fix this that bin/classes/<packagename> contains a few classes (BuildConfig.class, R$attr.class, R$drawable.class, R$layout.class, R$string.class, R.class), but not my class, HelloWorld, which is in src/<packagename>/HelloWorld.mirah

Stack trace:

W/dalvikvm(22599): threadid=1: thread exiting with uncaught exception (group=0x41af3700)
E/AndroidRuntime(22599): FATAL EXCEPTION: main
E/AndroidRuntime(22599): java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.kwiius.testah/com.kwiius.testah.HelloWorld}: java.lang.ClassNotFoundException: Didn't find class "com.kwiius.testah.HelloWorld" on path: DexPathList[[zip file "/data/app/com.kwiius.testah-2.apk"],nativeLibraryDirectories=[/data/app-lib/com.kwiius.testah-2, /vendor/lib, /system/lib]]
E/AndroidRuntime(22599):    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2271)
E/AndroidRuntime(22599):    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2405)
E/AndroidRuntime(22599):    at android.app.ActivityThread.access$600(ActivityThread.java:156)
E/AndroidRuntime(22599):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1272)
E/AndroidRuntime(22599):    at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(22599):    at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(22599):    at android.app.ActivityThread.main(ActivityThread.java:5303)
E/AndroidRuntime(22599):    at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(22599):    at java.lang.reflect.Method.invoke(Method.java:525)
E/AndroidRuntime(22599):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
E/AndroidRuntime(22599):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:555)
E/AndroidRuntime(22599):    at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(22599): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.kwiius.testah.HelloWorld" on path: DexPathList[[zip file "/data/app/com.kwiius.testah-2.apk"],nativeLibraryDirectories=[/data/app-lib/com.kwiius.testah-2, /vendor/lib, /system/lib]]
E/AndroidRuntime(22599):    at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:53)
E/AndroidRuntime(22599):    at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
E/AndroidRuntime(22599):    at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
E/AndroidRuntime(22599):    at android.app.Instrumentation.newActivity(Instrumentation.java:1061)
E/AndroidRuntime(22599):    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2262)
E/AndroidRuntime(22599):    ... 11 more
W/ActivityManager(  539):   Force finishing activity com.kwiius.testah/.HelloWorld

Any idea what could be causing this?

As a side note, it pindah dead? There hasn't been a commit or an issue in 8 months. Has it been replaced with a different project?

AtomicPair commented 10 years ago

Hi, @jj56. Let me look into this and report back my findings. In the meantime, what version of Pindah are you using?

The Pindah project has remained fairly quiet for most of this year. However, I have recently offered to manage the project myself, so you can expect to see several updates and bug fixes very soon.

AtomicPair commented 10 years ago

Hi, @jj56. Is this still an issue for you?

AtomicPair commented 10 years ago

@jj56 I've been unable to reproduce the problem on my end, and since we haven't heard from you in over two months, I'm going to close this issue. Please reopen if this is still a problem for you with the upcoming 0.1.3 release.