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.

Tom-ski have reported production level crash caused by EXC_BAD_ACCESS by java code inside try/catch block. It is well known issue of code like this:

    public static void sayHello() {
        String s = null;
        try {
            s.toString();
        } catch (NullPointerException e) {
            e.printStackTrace();
        }
    }

caused by third party code that messes with SIGSEGV signal handler and makes it not accessible to RoboVM.

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

Updated pods (ones with API changed)

• InMobi v10.8.3 -> v10.8.6
• IronSource v8.9.1 -> v8.10.0

Updates without any API change

• Facebook iOS Audience updated: v6.20.0 -> v6.20.1
• Branch Metrics updated: v3.12.1 -> v3.12.2
• Tenjin updated: v1.14.10 -> v1.14.11
• Unity updated: v4.15.1 -> v4.16.0
• CleverAds updated: v4.1.2 -> v4.3.0
• Google Mobile Ads updated to v12.7.0 -> v12.8.0

• Firebase updated to v12.0.0 -> v12.1.0

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

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