Developer disk images have been removed

[davidgiga1993]

Issue details

Deployment / Debug on iOS 17 devices doesn't work anymore

Related informations: https://developer.apple.com/forums/thread/730947
ios-control/ios-deploy#588

gradle launchIOSDevicex64
...
No DeveloperDiskImage.dmg found in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport for iOS version 17.0.1

my gradle file:

task launchIOSDevicex64(group: 'mobivm') {
	doLast {
		project.ext.'robovm.arch' = 'arm64'
	}
	finalizedBy launchIOSDevice
}

Configuration

Please provide the build system, version(s), and targets affected.

Build Tools:

• Gradle plugin

Versions:

Please provide the version of RoboVM, XCode and JDK used

• Robovm: 2.3.20
• XCode: 15.0
• JDK: temurin-17

Build Targets:

iOS 17 arm64

[dkimitsa]

yep it is not supported for a while due lack of support in dependency ilibmobiledevice.
work on replacement is in progress

[davidgiga1993]

Great, thanks a lot!

[davidgiga1993]

Do we need to wait for ilibmobiledevice? They mentioned that pymobiledevice3 supports it already, would that be an alternative to consider?

[dkimitsa]

pymobiledevice3 is not considered as alternative. the idea is to have same ecosystem solution (e.g. java) under own control. currently I'm porting pymobiledevice3 project into kotlin, to use as ilibmobiledevice replacement. Hope also to cover other connectivity issues we have. at least we will have it in own code base.

[davidgiga1993]

Any update on this? I can't really test on physical devices anymore which is a huge pain since the simulator doesn't provide the required functionality

[hooji]

I found a workaround that can be used to install MobiVM apps on physical devices using Apple provided command line tools.

1. Go to Mac App Store and download "Apple Configurator"
2. Create an alias: alias cfgutil='"/Applications/Apple Configurator.app/Contents/MacOS/cfgutil"'
3. Create an on-device run configuration and build your project. It will build, but then fail with an error trying to run on the device.
4. In Terminal, go to the build directory (like: ./robovm-build/tmp/on device/ios/arm64 ).
5. Your built app should be there (For example, "Main.app")
6. Run the command: cfgutil install-app ./Main.app

The app will install on your connected device (doesn't need to be unlocked), but will not automatically run.

You will need to search for your app by name to run it.

DONE!

PS: It would be nice if this could be integrated into the build process as an alternate installation method.

[obigu]

Just to clarify because I think it's not clear and the issue gives the impression it's not possible to deploy and app on an iOS 17 device.

Deployment of an app on a device works, it just fails on first launch with the "No DeveloperDiskImage.dmg found" message . After that you can launch the deployed app from springboard without issues (just clicking on the icon).

Debugging on the other hand doesn't work on device and the currrent workaround is to use Simulator.

[davidgiga1993]

Debugging on the other hand doesn't work on device and the currrent workaround is to use Simulator.

Sorry for the late reply, but this is exactly my issue as the simulator can only do so little. You can't properly test bluetooth, external usb connections, camera, and so on. Performance also can't be compared to physical devices.
So it's not a real workaround

[Andy-Whyte]

yep it is not supported for a while due lack of support in dependency ilibmobiledevice. work on replacement is in progress

Just wondering if iOS18 will ever be supported for Java? Would I be better moving to Kotlin?

[bitdream]

Any progress on this issue? It has been years. Are there any obstacle or just simply noboy working on it? It think this could be marked as No 1 bug for MobiVM now.

[hooji]

It will still install your app on your device. It's just the auto-launch that is broken. Took me a while to figure that out.

…

On Fri, Apr 4, 2025 at 5:11 PM 10xBot ***@***.***> wrote: Any progress on this issue? It has been years. Are there any obstacle or just simply noboy working on it? It think this could be marked as No 1 bug for MobiVM now. — Reply to this email directly, view it on GitHub <#755 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOUB3A4OLE3BYWXVJW223D2X5CURAVCNFSM6AAAAAA5YLONP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBQGE3DMMRQG4> . You are receiving this because you commented.Message ID: ***@***.***> [image: bitdream]*bitdream* left a comment (MobiVM/robovm#755) <#755 (comment)> Any progress on this issue? It has been years. Are there any obstacle or just simply noboy working on it? It think this could be marked as No 1 bug for MobiVM now. — Reply to this email directly, view it on GitHub <#755 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOUB3A4OLE3BYWXVJW223D2X5CURAVCNFSM6AAAAAA5YLONP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBQGE3DMMRQG4> . You are receiving this because you commented.Message ID: ***@***.***>

[bitdream]

It will still install your app on your device. It's just the auto-launch
that is broken. Took me a while to figure that out.
…

We need to see the log.
When I first saw the error message, I thought my iphone OS version too new while my Xcode is a bit outdated. Several months later after I upgraded both iphone and xcode to the latest iOS version, the message is still there and then I realize it's a bug of MobiVM.
BTW, simulator doesn't equal device. I have the experience that in simulator everything works well but in device it crashed.

[dkimitsa]

hey, it a bit delayed as it was not supported with external dependency we use to deploy to device (libmobiledevice).
currently I'm playing around implementing similar functionality but in kotlin that we can use with RoboVM.

[bitdream]

hey, it a bit delayed as it was not supported with external dependency we use to deploy to device (libmobiledevice). currently I'm playing around implementing similar functionality but in kotlin that we can use with RoboVM.

Hi, thanks. I am relieved to know it is ongoing. We can wait and use older devices for testing now. If you need a hand or test support or any help, post in thread maybe we (the users) can also help🥳

[davidgiga1993]

Any update on this? :)