RoboVM 1.12 Released - Experimental tvOS support, iOS 9.2

[Niklas Therning]

Hi,

We are excited to announce the release of RoboVM 1.12. This release brings experimental tvOS support, bindings for iOS 9.2 and more!

Head over to our blog for the full details (https://robovm.com/robovm-1-12-released-experimental-tvos-support), including other new features and bug fixes!

Regards,

Niklas Therning

and the RoboVM team

[Michael Pujos]

Under Eclipse, attempting to an iOS app on a real device running 9.2 results in an error popup with test:

Launch failed. Check the RoboVM console for more information.
The given data is not a property list of a supported format.


The failure happens just after the execution of codesign which is successful (I could verify, running the command in a shell).

So what property list could be invalid ?

It runs fine in the emulator.

[Michael Pujos]

On Thursday, 17 December 2015 15:36:52 UTC+1, Michael Pujos wrote:

Under Eclipse, attempting to an iOS app on a real device running 9.2 results in an error popup with test:

This line should read:

Under Eclipse, attempting to run an iOS app on a real device running 9.2 results in an error popup with text:
 

[Niklas Therning]

Have you used that device for development before? Can you launch on it successfully from within Xcode? Would you mind sending us you Eclipse log file and the output you see in the "RoboVM Console" in Eclipse? See http://docs.robovm.com/errors.html for more info on how to get the logs and console output.

--
You received this message because you are subscribed to the Google Groups "RoboVM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robovm+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Pujos]

- I can run a regular iOS app from Xcode without problem.

- However, the last time I sent the problematic iOS app from Eclipse, the iOS device (and iPhone 6+) was still running 9.1, and it was with RoboVM 1.11.
So this is the first time I'm trying to run the app on my device updated to 9.2.


Here's the Eclipse log, hopefully helpful with a stack trace:

!ENTRY org.robovm.eclipse 4 0 2015-12-17 15:35:30.265
!MESSAGE Launch failed. Check the RoboVM console for more information.
!STACK 0
java.io.IOException: The given data is not a property list of a supported format.
        at org.robovm.compiler.target.ios.AppleDeviceTarget.getConnectedDevices(AppleDeviceTarget.java:403)
        at org.robovm.compiler.target.ios.AppleDeviceTarget.createDeviceLauncher(AppleDeviceTarget.java:282)
        at org.robovm.compiler.target.ios.AppleDeviceTarget.createLauncher(AppleDeviceTarget.java:172)
        at org.robovm.compiler.target.AbstractTarget.doLaunch(AbstractTarget.java:486)
        at org.robovm.compiler.target.ios.AppleDeviceTarget.doLaunch(AppleDeviceTarget.java:777)
        at org.robovm.compiler.target.AbstractTarget.launch(AbstractTarget.java:482)
        at org.robovm.compiler.AppCompiler.launchAsync(AppCompiler.java:840)
        at org.robovm.eclipse.internal.AbstractLaunchConfigurationDelegate.launch(AbstractLaunchConfigurationDelegate.java:292)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.dd.plist.PropertyListFormatException: The given data is not a property list of a supported format.
        at com.dd.plist.PropertyListParser.parse(PropertyListParser.java:216)
        at org.robovm.compiler.target.ios.AppleDeviceTarget.getConnectedDevices(AppleDeviceTarget.java:397)
        ... 12 more


And here's the end RoboVM console output (the rest has no error, so not relevant). codesign is not failing:

12/17/15 3:35:29 PM: [ INFO] codesign -f -s <edited> --entitlements /<edited path>/ios/thumbv7/Entitlements.plist /<edited path>/ios/thumbv7/Main.app
12/17/15 3:35:30 PM: [ERROR] Launch failed

[Niklas Therning]

Please run

  system_profiler -xml SPUSBDataType

in a Terminal and let us know what it outputs.

--

[Michael Pujos]

Sent to your email address.

[Niklas Therning]

Ok. This should be fixed in the next nightly build which will be available sometime around 03:00 (GMT+1). Please give it a try and report back. For instructions on how to use nightly builds please see http://docs.robovm.com/advanced-topics/nightlies.html.

On Thu, Dec 17, 2015 at 5:35 PM, Michael Pujos <pujos....@gmail.com> wrote:

Sent to your email address.

--

[Michael Pujos]

On Thursday, 17 December 2015 19:18:29 UTC+1, Niklas Therning wrote:

Ok. This should be fixed in the next nightly build which will be available sometime around 03:00 (GMT+1). Please give it a try and report back. For instructions on how to use nightly builds please see http://docs.robovm.com/advanced-topics/nightlies.html.

Confirming this is fixed since the 12/18 nightly.

[Niklas Therning]

It seems to be a rare problem, due to a USB hub. We've never seen it during our tests.

On Sat, Dec 19, 2015 at 2:05 PM, Tom <tan...@gmail.com> wrote:

Does it mean some serious bugs will be fixed in the next year? 

--

[Kirill Prazdnikov]

Important: our deploy was broken after this release, the reason was maven plugin configuration changes:

-          <iosSignIdentity>${robovm.iosSignIdentity}</iosSignIdentity>
-          <iosProvisioningProfile>${robovm.iosProvisioningProfile}</iosProvisioningProfile>
+          <signIdentity>${robovm.iosSignIdentity}</signIdentity>
+          <provisioningProfile>${robovm.iosProvisioningProfile}</provisioningProfile>

[Niklas Therning]

That was unfortunate. Thanks for the heads up. We added aliases so if you use -Drobovm.iosSignIdentity from the command line it will still work. But we must have overlooked how it works when configured from within the POM.

--

[Kirill Prazdnikov]

Can we expect announcements about such incompatible changes in the future ?

We have complex infrastructure with automated build\deploy, which was broken  after 1.12.

Also the RoboVM did not say a message about "iosSignIdentity" is no more supported and deprecated.

We added aliases 

To which release ?

Thanks 

[Niklas Therning]

It was a mistake on our part. We didn't intend to remove the iosSignIdentity property completely. The alias only applies if you use -Drobovm.iosSignIdentity=... on the Maven command line. That will still work.

[James Cook]

Hi Niklas,

Thanks for providing a fix so quickly for this. I too experienced it, and the 1.12.1-SNAPSHOT worked for me. However the latest snapshot seems to cause this error when I try to launch on device.

Caused by: org.gradle.api.GradleException: Failed to launch IOS Device

at org.robovm.gradle.tasks.IOSDeviceTask.invoke(IOSDeviceTask.java:48)

Caused by: java.lang.UnsatisfiedLinkError: org.robovm.compiler.util.io.HfsCompressor.compressNative(Ljava/lang/String;[BI)Z

at org.robovm.compiler.util.io.HfsCompressor.compressNative(Native Method)

at org.robovm.compiler.util.io.HfsCompressor.compress(HfsCompressor.java:58)

at org.robovm.compiler.ClassCompiler.generateMachineCode(ClassCompiler.java:432)

at org.robovm.compiler.ClassCompiler.access$000(ClassCompiler.java:133)

at org.robovm.compiler.ClassCompiler$1.run(ClassCompiler.java:330)

My code didn't change just it grabbed the latest snapshot.

Cheers

James

[Niklas Therning]

Hmmm, I just tried the latest nightly build via Gradle and didn't see this problem. Could be a Gradle daemon problem. Run "jps" in Terminal and kill all running GradleDaemon processes (or run "gradle --stop"). Retry your gradle build and see if that fixes the issue.

[James Cook]

Yea I think you are right. I tried three different projects last night and different versions of RoboVM and they had differing results. Will suggest what you propose and let you know.