Gluon Mobile：ResourceBundle与class.getResource无法加载资源及移植报错

Hey there! I’ve dealt with this exact problem when porting JavaFX apps to Gluon Mobile, so let’s break down what’s happening and how to fix it.

Why This Happens #

Gluon Mobile uses GraalVM Native Image to build apps for iOS (and other mobile platforms). Unlike the standard JVM (which loads classes dynamically at runtime), Native Image performs a static analysis of your code during the build process. Any classes loaded dynamically via Class.forName() (like the ObjectDB locale class here) won’t be included in the native image unless you explicitly tell GraalVM to link them. That’s why your app works on desktop but crashes on the iPad simulator.

Step-by-Step Solutions #

Option 1: Use the -forcelinkclasses Command Line Argument #

When building your native image, add the -forcelinkclasses flag to specify the class (or a wildcard pattern for multiple classes) that needs to be included. For example:

-native-image -forcelinkclasses com.objectdb.ui.language.Locale_en_EN -jar your-app.jar

If you think there might be other locale classes or related classes from ObjectDB that need linking, use a wildcard to cover all of them:

-native-image -forcelinkclasses com.objectdb.ui.language.* -jar your-app.jar

Option 2: Configure in Your Gradle Build Script (Recommended for Gluon Projects) #

Most Gluon Mobile projects use Gradle, so you can set this directly in your build.gradle file. Look for the nativeImage block and add the forceLinkClasses configuration:

nativeImage {
    // Other existing arguments (like enable HTTP/HTTPS)
    args('--enable-http', '--enable-https')
    
    // Add this line to force link the required classes
    forceLinkClasses = [
        'com.objectdb.ui.language.*'
    ]
}

This ensures the setting is applied every time you build your native image, avoiding manual command line flags.

Extra Tips #

• If you’re still having issues, you can widen the pattern to include the entire ObjectDB package (note: this will increase your app’s size):

  forceLinkClasses = [
      'com.objectdb.**'
  ]
  

• Make sure you’re using the latest version of the Gluon Gradle Plugin and GraalVM Native Image, as newer versions fix many class linking edge cases.

After applying one of these solutions, rebuild your native image and test it on the iPad simulator—your app should start up without the Class.forName() error now!

内容的提问来源于stack exchange，提问作者Juan