App crashing with “Stub!” error

[SFenton]

I'm playing around with trying to add the react-native-dualscreeninfo to my existing React Native project. However, when adding the gradle requirements to get it running (just the Kotlin version, and I've also added the maven for the SDK feed), I annoyingly just get a crash that says "Stub!". I can't screenshot it in the app- it just crashes- but here's a stack from Android Studio:

Frustratingly, I can get the example projects to build and run, so I think it's something in my proj
ect setup, and not the emulator.

Has anyone run into this and been able to get around it? Very excited to start developing, but this roadblock is a big one.

[conceptdev]

I noticed a similar post on Stack Overflow (crosspost?), transferring the answer here for reference: similar issue was tracked down to Proguard/R8 in release builds where minification was enabled. Added

-keep class com.microsoft.device.display.** { *; }

to fix the problem. Thanks Sapph for the answer.

[chrisglein]

@conceptdev Thanks for the link and the fix information! Is there something that needs to change in the config for react-native-dualscreen or is this something for the general app config?

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[conceptdev]

The "Stub" error is an indicator that the project isn't including the DisplayMask library, so compare your Android project's gradle files against the samples... you'll need the following in build.gradle lines 42-44

        maven {
            url 'https://pkgs.dev.azure.com/MicrosoftDeviceSDK/DuoSDK-Public/_packaging/Duo-SDK-Feed/maven/v1'
        }

and line 52

implementation "com.microsoft.device.display:display-mask:0.3.0"

(in the correct locations). That should get things working, if the samples are already working for you.

If you already have that set in your Android project folder and still get the error, then it could be release proguard configuration. The Android Studio docs have some info. This wouldn't typically be set-up by default, so you shouldn't need to venture down this path unless it's something that's been added to your project...

Check if you have a proguardFiles entry in your gradle files - if you do and it's pointing to a proguard-rules.pro file, that's where you can enter the hint to keep the lib:

-keep class com.microsoft.device.display.** { *; }

Here's a random example of that file from the MSAL library which also uses DisplayMask. Note that the filename is different - that's something that can be changed in the gradle references.