Copying older RoboVM jar version together with current version.

[rotter]

When I run my game on my device I noticed today (might be an old issue) that when uploading the files to the device it uploads 2 versions of some RoboVM jars (version beta-03 and beta-04, then beta-03 and 1.0.0 after I updated).

I dont know if this causes any bigger problems or not (seems to run fine), so I asked for help on this problem on the RoboVM google group. Mario tried to help me and we didn't find the issue, he suggested opening an issue here, but honestly we cant know if this is a bug from RoboVM plugin.

Please see the thread here:
https://groups.google.com/forum/#!topic/robovm/LlvUbu-WD3M

What I have tried:

• Updated RoboVM version on build.gradle (from 1.0.0-beta-04 to 1.0.0)
• Updated LibGDX version on build.gradle (from 1.5.4 to 1.5.5)
• Updated robovm-gradle-plugin version on build.gradle (from 1.0.0 to 1.0.0-beta-01)
• Reinstalling the RoboVM plugin (already had the latest version)
• Updating the Gradle plugin (from 3.6.3 to 3.6.4)
• Check the dependencies using ./gradlew ios:dependencies (no references to beta-03)

Any ideas what I can try, or any more info needed?

Best

[rotter]

Ok, I have found the culprit!

I use some iOS bindings (for example Admob) that are linked to RoboVM beta-03. It doesnt show on gradlew ios:dependencies because they are not linked through Gradle (I have added the project dependency manually).

I have no idea, tho, on how to update the linked RoboVM version on that project (couldn't find on any config file).

But still the problem was apparently found, so don't worry about this issue, feel free to close (I guess) - sorry!

[badlogic]

Great find, thanks for reporting back.
On Mar 18, 2015 10:30 PM, "rotter" [email protected] wrote:

Ok, I have found the culprit!

I use some iOS bindings (for example Admob) that are linked to RoboVM
beta-03. It doesnt show on gradlew ios:dependencies because they are not
linked through Gradle (I have added the project dependency manually).

I have no idea, tho, on how to update the linked RoboVM version on that
project (couldn't find on any config file).

But still the problem was apparently found, so don't worry about this
issue, feel free to close (I guess) - sorry!

—
Reply to this email directly or view it on GitHub
#37 (comment)
.