Open GoogleCodeExporter opened 9 years ago
I also have the same problems and no help in the Google forums ... I think this
project was abandoned and forgotten to notify us ...
It has several errors that meeting following the guidelines of the page and
Starter been looking on the net and many people have the same problem!
Original comment by rick....@gmail.com
on 20 Jan 2012 at 12:15
Yep. It's abandoned. No one here but us chickens.
Original comment by m...@samskivert.com
on 20 Jan 2012 at 4:23
Couldn't you use the "mvn android:deploy" command instead ?
And AFAIK, I think it was said somewhere that PlayN apps doesn't run yet on the
emulator... You need a real device in order to test your application.
Maybe it's fixed now, but last time I tried, the emulator didn't run PlayN apps
correctly :-\
Original comment by mbarbe...@gmail.com
on 20 Jan 2012 at 5:58
The Android emulator is *extremely* slow. It is not a viable way to test your
Android games. Test them using the Java backend during development, and when
you're ready to test them on an actual device, test them on an actual device.
It would be a waste of my or any other PlayN developer's time to get things
working on the emulator.
Original comment by samskiv...@gmail.com
on 20 Jan 2012 at 6:09
Well, last time I ran a PlayN app on the emulator, it simply crashed... I read
somewhere (maybe on the Google Group ?) that the emulator didn't run PlayN at
all.
But, that's true the emulator is really slow whatever you try to do, so the
best is to own a real device for testing purpose...
Original comment by mbarbe...@gmail.com
on 20 Jan 2012 at 6:51
I can't run the samples on Android as well. "mvn android:deploy" doesn't
work... see issue 122. It gives errors about dependencies which can't be
resolved, because certrain resources can't be found.
Original comment by paul.wol...@googlemail.com
on 29 Jan 2012 at 10:12
Original issue reported on code.google.com by
na...@trymph.com
on 20 Jan 2012 at 11:08