Setup libGDX project using MOE plugin

How to setup the libGDX project using MOE plugin.
If i try to select ios-moe at the setup of libGDX project then my build fails with following error.

Generating app in /Users/USERNAME/Desktop/PaxPlay/libGDXProjects/SampleGame
Executing ‘/Users/USERNAME/Desktop/PaxPlay/libGDXProjects/SampleGame/gradlew clean --no-daemon’
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon:
Configuration on demand is an incubating feature.

FAILURE: Build failed with an exception.

  • What went wrong:
    A problem occurred configuring root project ‘SampleGame’.

Could not resolve all dependencies for configuration ‘:classpath’.
Could not find
Searched in the following locations:
Required by:

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.


Total time: 8.492 secs
To import in Eclipse: File -> Import -> Gradle -> Gradle Project
To import to Intellij IDEA: File -> Open -> build.gradle
To import to NetBeans: File -> Open Project…

Hi Rohit,

LibGDX is being updated to the new open source version of MOE. Once it is done, it will be announced both here and at LibGDX. Please stay tuned.

Best Regards,

Till then is there any other way?

Tom-Ski already committed the MOE backend updates to libgdx, so it might be already available (or will be available soon) in the libgdx nightlies, that you could try out.

Still having the same issue.

The project is build successfully after the new setup tool is released. But now it seems there are few sync issues?

I am getting compiler error for IOSMoeLauncher class.
Error:(13, 13) Gradle: error: cannot access Pointer
class file for not found

at this function
protected IOSMoeLauncher(Pointer peer) {

Dear PaxPlayer,

Whenever you see a failure with a class package starting with, that means it is trying to use code from an older MOE version. Please upgrade your code to use the new classes which have a package prefix of

Hi liliomk,
I have updated the MOE plugin already and created a fresh project using the new setup tool.
This is my auto generated IOSMoeLauncher.Java class. Don’t think I can do much here. Any ideas?

package com.example.samplegame;

import com.badlogic.gdx.backends.iosmoe.IOSApplication;
import com.badlogic.gdx.backends.iosmoe.IOSApplicationConfiguration;
import com.example.samplegame.MyGdxGame;

import ios.uikit.c.UIKit;

public class IOSMoeLauncher extends IOSApplication.Delegate {

    protected IOSMoeLauncher(Pointer peer) {

    protected IOSApplication createApplication() {
        IOSApplicationConfiguration config = new IOSApplicationConfiguration();
        config.useAccelerometer = false;
        return new IOSApplication(new MyGdxGame(), config);

    public static void main(String[] argv) {
        NSAutoreleasePool pool = NSAutoreleasePool.alloc();
        UIKit.UIApplicationMain(0, null, null, IOSMoeLauncher.class.getName());

So above issue resolves if you change the libGDX version to 1.9.5-SNAPSHOT and there are no more compiler error after that however there are still issues with the plugin.

When I tried to run the app on iOS this is what I got

fatal error: ‘MOE/MOE.h’ file not found
include <MOE/MOE.h>
1 error generated.


The following build commands failed:
CompileC /Users/rohitgoyal/Desktop/PaxPlay/libGDXProjects/SampleGame/ios-moe/build/moe/xcodebuild/obj/ ios-moe/main.cpp normal i386 c++
CompileC /Users/rohitgoyal/Desktop/PaxPlay/libGDXProjects/SampleGame/ios-moe/build/moe/xcodebuild/obj/ ios-moe/main.cpp normal x86_64 c++

(2 failures)

I got the same issue MOE/MOE.h not found
on multi-os engine1.2.0 and libgdx 1.9.5-SNAPSHOT.
Any advice ?

Was it a newly generated project using gdx-setup or an existing project updated to the new version?

For an existing project you will need to update the Xcode project as well. The easiest way would be if you could just replace your old Xcode project with a newly generated one, and re-add any necessary sources.

Here is a topic about the same issue:

Thank you for your reply.
I used this :

And I dont have this error anymore