Tom-Ski on master
* fixed: de-sugared ByteBuffer … Merge pull request #668 from dk… (compare)
Tom-Ski on master
* fixed #673: allow x86_64 arch… Merge pull request #675 from dk… (compare)
Tom-Ski on master
* fixed 682: Subscription APIs … Merge pull request #683 from dk… (compare)
Libcore 12 (was 10) update, build 3 v10.2.2
Major changes to Libcore10 experiment:
bro-bridgeseparated from RT code into stand-alone library;
@ForceLinkClassannotation moved to RT code from
bro-bridgeand now recognised and processed by compiler. Otherwise methods might be dropped if not directly used in Java code which breaks references from JNI;
@ForceLinkClassannotation to reference dependencies in places where classes are used indirectly. It makes RoboVM usage more smooth for beginners e.g. they don't need to bother with ClassNotFound exceptions in very basic code
Also updated with MobiVM base and it includes changes from 2.3.18 release
Idea snapshot is attached to release page
Also artefacts deployed to
sonatype repository and accessible in
com.rovovmx group under
I am testing robovm with a Mac M1 and when I run the gradle command to launch the app.
./gradlew clean launchIPhoneSimulator -Probovm.arch=arm64
I get the error:
Failed to execute the task ':launchIPhoneSimulator'. > A matching device could not be found [arch=arm64-simulator, family=iPhone, name=null, version=null]
If I don't specify the architecture, it works but compiles for x86_64.
... > Task :launchIPhoneSimulator Caching disabled for task ':launchIPhoneSimulator' because: Build cache is disabled Task ':launchIPhoneSimulator' is not up-to-date because: Task has not declared any outputs despite executing actions. Building RoboVM app for: ios (x86_64-simulator) ...
Hi, I just got log like this:
Cannot find an ad network adapter with the name(s): GADMAdapterUnity. Remember to link all required ad network adapters and SDKs, and set -ObjC in the 'Other Linker Flags' setting of your build target.
After I add unity ad framework and unity ad adapter framework in lib
In older versions of robovm
UIWindow.Notifications.observeKeyboardWillShow returned an NSObject object. In newer versions of robovm it returns a NSObjectProtocol.
What would be the correct way to remove this (NSObjectProtocol) observer?
For older versions I was using
NSNotificationCenter.getDefaultCenter().removeObserver but the argument it's a NSObject.
I'm struggling with uploading my IPA for Test Flight:
"Asset validation failed (90161)
Invalid Provisioning Profile. The provisioning profile included in the bundle com.example394.app [Payload/IOSLauncher.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal. (ID: 7c6772a9-e092-4a35-8313-1150a7e293c0)"
How can I get past this error?
ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics/FirebaseCore.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics/FirebaseCoreDiagnostics.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics/FirebaseInstallations.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics/GoogleDataTransport.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics/GoogleUtilities.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics/nanopb.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAnalytics/PromisesObjC.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAuth/FirebaseAuth.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseAuth/GTMSessionFetcher.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseCrashlytics/FirebaseCrashlytics.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseMessaging/FirebaseInstanceID.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseMessaging/FirebaseMessaging.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/FirebaseMLModelInterpreter/Protobuf.xcframework/ios-armv7_arm64' ld: warning: directory not found for option '-F/Users/runner/work/wordsy/wordsy/ios/libs/Google-Mobile-Ads-SDK' ld: framework not found FirebaseAnalytics clang: error: linker command failed with exit code 1 (use -v to see invocation)
hey folks! I'm trying to symbolicate a crash report here but the
atos command line tool is not providing me good results
atos -o IOSLauncher.app/IOSLauncher -arch arm64 -l 0x104a1c000 0x000000010653e610
0x0000000101b22610 (in IOSLauncher) + 128
any ideas of what I'm doing wrong?
[ERROR] 22:13:17.155 Undefined symbols for architecture arm64: [ERROR] 22:13:17.155 "_[j]java.lang.Object.getClass()Ljava/lang/Class;[lookup]", referenced from: [ERROR] 22:13:17.159 _[J]com.esotericsoftware.spine.SkeletonRenderer.draw(Lcom/badlogic/gdx/graphics/g2d/Batch;Lcom/esotericsoftware/spine/Skeleton;)V in SkeletonRenderer.class.o [ERROR] 22:13:17.383 ld: symbol(s) not found for architecture arm64 [ERROR] 22:13:17.431 clang: error: linker command failed with exit code 1 (use -v to see invocation) [ERROR] Couldn't compile app
Hi there! Does anyone know of any reason why the dSYM file generated by createIPA would be empty? (no debug information whatsoever). What is odd is that this happens only sometimes, and other times the dSYM is correctly generated. From the logs I can't see any errors either:
... Installing Info.plist to /Users/runner/game/ios/build/robovm/IOSLauncher.app xcrun dsymutil -o /Users/runner/game/ios/build/robovm/IOSLauncher.app.dSYM /Users/runner/game/ios/build/robovm/IOSLauncher.app/IOSLauncher xcrun strip -x /Users/runner/game/ios/build/robovm/IOSLauncher.app/IOSLauncher ...
(the logs output is the same when the dSYM is 'corrupted' when comparing to when it is correct)
Using robovm 2.3.18. What could I try to obtain more information about the results of the generation of the dSYM folder contents?
Thanks in advance
[ERROR] Couldn't start application
roboVMVersion = '2.3.18'
[ERROR] Couldn't start application
roboVMVersion = '2.3.18'
resolved-substituted the correct certificate
Hello there, I try to launch my App via Gradle Command Line on my device which currently fails for not providing a signing identity and provisioning profile via command line. (My build-gradle has the identities for distribution configured) for developing I use different credentials.
How do I pass those via command line?
2022-09-28 11:23:59.170 INFO: Show Progress: Analyzing package…
2022-09-28 11:25:02.619 INFO: Show Progress: Sending analysis to App Store Connect…
2022-09-28 11:25:04.218 INFO: COMPLETED - PART 1
2022-09-28 11:25:04.337 INFO: COMPLETED - PART 2
2022-09-28 11:25:04.341 INFO: Show Progress: Waiting for App Store Connect analysis response…
2022-09-28 11:25:41.293 ERROR: Asset validation failed (90179) Invalid Code Signing. The executable 'Payload/com.xxxx.ios.app/com.xxxx.ios' must be signed with the certificate that is contained in the provisioning profile. (ID: xxxxxx)
I have got this error, I have completely rechecked my certificate, what gone wrong?
@dkimitsa: Is there a recommended way of getting Runtime Only project dependencies into RoboVM?
We have started restructuring our project to be less monolithic and only give direct access to project direct access is really needed to, so there are a few dependencies only provided via "implements" in gradle instead of "api". IDEA Marks them as runtime only.
Compilation with RoboVM works fine, but launching the app results in NoClassDefFoundErrors when one of my actual dependencies tries to access those.
If I make sure to manually build that dependency so there is a jar in its respective lib folder it works correctly, but apparently when robovm is doing its thing it seems to not bother compiling runtime dependenies, while those obviously also have to be present in RoboVM Runtime.
I am trying to workaround it by having a fat jar built that includes runtime dependencies, but this feels a little wrong to me, so I was wondering if I am doing something wrong.
My project tree looks like this Root
Persistence has WebAPI marked as implements because its not supposed to be exposed to iOS.
iOS has Persistence marked as implements. And therefore gets a Runtime Only dependency to WebAPI
It would probably work if I set WebAPI to "api" in gradle, but I dont want direct access to Web-API in my iOS Project.
Do you have any idea?