There are two major updates regarding AltPods:

• v1.56.0 was released to Maven Central.
• The approach to versioning has changed.

Breaking Changes: Migration from bundle versions to individual pod versions

Previous drawbacks:

• A single version number was used for all modules within an alt-pod release. For example, alt-pods v1.56.0 contained Firebase Crashlytics v1.56.0, even though the actual bindings corresponded to 12.7.0.
• All modules were released under the new alt-pods version, even if no changes were made to them.
• Incompatible binding versions were sometimes grouped under a single alt-pods umbrella (e.g., an ads library might not be compatible with the Google Ads mediator if the latest version wasn’t available yet).

What has changed:

• Each module now has its own version built from the binary version. For example, if SomeFramework is vA.B.C, the pod version will be vA.B.C.0. The .0 suffix allows for future patch versions.
• Each module is now independent and can be deployed separately.
• There is no longer a need to deploy pods that haven’t received updates.
• Snapshot versions will no longer be used for periodic updates. Only new frameworks currently under testing might be deployed as snapshots.

The artifacts for v1.56.0 have already been deployed under their own independent versions to Maven Central and are ready for testing.
The upcoming v1.57.0 delivery is a work in progress, as it requires script adaptations, but it is expected to be available for testing later this week.

View the migration source code on GitHub

Please open an issue if you encounter any bugs.

AltPods v1.55.0 were released to Maven central.
New scan performed to sync with recent releases and available for testing as v1.56.0-SNAPSHOT.

Updated pods (ones with API changed)

• CleverAds v4.4.2 to v4.5.4
• Fyber v8.4.1 to v8.4.2
• Google Mobile Ads v12.12.0 to v12.14.0
• InMobi v11.0.0 to v11.1.0
• IronSource v9.0.0 to v9.2.0
• HelpShift v10.4.1 to v10.5.0
• Singular v12.9.0 to v12.9.2
• Tenjin 1.14.5 to 1.14.7

• UnityAds v1.14.11 to v1.15.0

• These pods were pushed to https://central.sonatype.com/repository/maven-snapshots/ maven repo under 1.56.0-SNAPSHOTS version. Source code @github

Updates are not fully tested, please open issue if bug found.

AltPods v1.54.0 were released to Maven central. New scan performed to sync with recent releases and available for testing as v1.55.0-SNAPSHOT.

Updated pods (ones with API changed)

• AppLovinSDK v13.4.0 -> v13.5.0
• CleverAds v4.3.0 -> v4.4.2
• OneSignal v5.2.14 -> v5.2.15

• Singular v12.8.1 -> v12.9.0

• These pods were pushed to https://central.sonatype.com/repository/maven-snapshots/ maven repo under 1.55.0-SNAPSHOTS version. Source code @github

Updates are not fully tested, please open issue if bug found.

As continue of investigating deadlock:

Thread #17 also displays strange stacktrace that normally should not happen:

• native(ObjC code) calls [myObject description];
• tries to marshal pointer(handle) to Java object in toObjCObject;
• it doesn’t find it in peer map and creates new Java instance/wrapper using ObjCObject.createInstance.

What is completely wrong here:

Due to a deadlock, a synchronization object in ObjC-related code became unavailable, causing the application to hang while trying to acquire a lock on it. It could also crash if the garbage collector (GC) was involved at that moment:

[ERROR] android.System: com.example.TestObject.finalize() timed out after 10 seconds
[ERROR] android.System: java.util.concurrent.TimeoutException: com.example.TestObject.finalize() timed out after 10 seconds
    at org.robovm.objc.ObjCObject$ObjectOwnershipHelper.release(ObjCObject.java:525)
    at org.robovm.objc.ObjCRuntime.void_objc_msgSend(Native Method)
    at org.robovm.apple.foundation.NSObject.release(NSObject.java:228)
    at org.robovm.apple.foundation.NSObject.doDispose(NSObject.java:212)
    at org.robovm.objc.ObjCObject.dispose(ObjCObject.java:148)
    at org.robovm.objc.ObjCObject.finalize(ObjCObject.java:135)
    at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:172)
    at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:155)
    at java.lang.Thread.run(Thread.java:869)

Getting the stack traces

AltPods were updated to v1.54.0-SNAPSHOT to sync with recent releases.

Updated pods (ones with API changed)

• BranchMetrics v3.13.0 -> v3.13.3
• Firebase v12.2.0 -> v12.4.0
• Fyber v8.3.8 -> v8.4.0
• HelpShift v10.4.0 -> v10.4.1
• IronSource v8.11.0 -> v9.0.0
• InMobi v10.8.6 -> v11.0.0

• UnityAds v4.16.1 -> v4.16.3

• These pods were pushed to https://central.sonatype.com/repository/maven-snapshots/ maven repo under 1.54.0-SNAPSHOTS version. Source code @github

Updates are not fully tested, please open issue if bug found.

Few months since last Tracking slipped NPE and here we go again:

• same user reported;
• same scenario (code that handles a lot of NPE in try/catch);
• this time with Crashlytics.

Time for dissection…

There was a report in MobiVM matrix channel for crash that is happening only during running under debugger:

java.lang.NoClassDefFoundError: Could not initialize class com.sample.mobile.ios.network.RoboVmNetzwerkStatusController
        at com.sample.mobile.ios.Main.didFinishLaunching(Main.java:208)
        at com.sample.mobile.ios.Main.$cb$application$didFinishLaunchingWithOptions$(Main.java)
        at org.robovm.apple.uikit.UIApplication.main(Native Method)
        at org.robovm.apple.uikit.UIApplication.main(UIApplication.java:442)
        at com.sample.mobile.ios.Main.main(Main.java:314)

TLTR: Fix and workaround

AltPods were updated to v1.53.0-SNAPSHOT to sync with recent releases.

Updated pods (ones with API changed)

• AppsFlyer v6.17.2 -> v6.17.4
• AppLovinSDK v13.3.1 -> v13.4.0
• BranchMetrics v3.12.2 -> v3.13.0
• IronSource v8.10.0 -> v8.11.0

Updates without any API change

• Google Mobile Ads updated to v12.8.0 -> v12.9.0
• Firebase updated to v12.1.0 -> v12.2.0

• UnityAds updated: v4.16.0 -> v4.16.1

• These pods were pushed to https://central.sonatype.com/repository/maven-snapshots/ maven repo under 1.53.0-SNAPSHOTS version. Source code @github

Updates are not fully tested, please open issue if bug found.

issue#813 was reported as an issue with storekit2 bindings.

Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘+[missing_RvmProduct_PurchaseOption appAccountToken:]: unrecognized selector sent to class 0x1332748a0’

With comments that simulator works but app fails on real device.
Lets investigate.