CallToActionView Not Responding to Press on Android

[hongjae-eum]

MAX Module Version

7.0.1

React Native Version

0.73.6

Device/Platform Info

Android 14

Current Behavior

The CallToActionView inside NativeAdView is not responding to presses on Android. The TitleView and MediaView work fine. The CallToActionView is wrapped with TouchableOpacity.

It seems that the onPress event is not being passed through when wrapped with TouchableOpacity.

This issue is specific to Android. On iOS, it works correctly.

Expected Behavior

No response

How to Reproduce

When using the CallToActionView inside NativeAdView, there is no response when it is touched on Android.

Additional Info

If I remove TouchableOpacity, the CallToActionView works, but this may not be the ideal solution.

[hongjae-eum]

Screen_Recording.mp4

[alhiwatan]

@hongjae-eum, thanks for raising this issue. It might be caused by how the CTA is laid out with your UI components or a combination of layout and props. Since the CTA works with our example on Android, could you try adjusting your layout or props to make it work? If that doesn't resolve the issue, could you send us a demo program? Also, let us know if this issue is reproduced with a specific ad network.

[hongjae-eum]

@alhiwatan
I have reproduced the issue using the provided example code (this repo). I only changed the app package, SDK_KEY, NATIVE_AD_UNIT_ID, and turn off preloading.(when I enable preloading, the app crashes.)

The issue occurs on Android in the same way.
Actually, this bug was also found in version 6.5.0.

Please refer to the attached video for more details.

Screen_Recording_20240723_140807_Google.Play.Store.1.mp4

[hongjae-eum]

@alhiwatan
Have you checked my response and the video? If you need any further information or updates, please let me know.

[alhiwatan]

@hongjae-eum , thank you for updating us on the issue. Unfortunately, we are unable to reproduce it on our end. Could you please enable verbose logging and send us the logs so we can investigate further?

[hongjae-eum]

@alhiwatan
I executed AppLovinMAX.setVerboseLogging(true); to generate logs, but I do not see any logs.

The app is an example code from your repository, and I added setVerboseLogging. The physical device used is registered as a test device.

However, no logs are appearing. Is there any other action required to view the logs?

[alhiwatan]

@hongjae-eum, the verbose logging logs are printed as a log of Android system messages. You can view them with adb logcat or in the Android studio.

[hongjae-eum]

@alhiwatan

I am attaching the logcat records.(The SDK key and package name have been replaced with different values.)
samsung-SM-G996N-Android-14_2024-08-12.txt

Since the content is extensive, I filtered it using "applovin". If you need any other filtering, please let me know.
The scenario is as follows: App launch -> Click "Show Native Ad" -> Click the CTA button, but no action occurs (about 10 times).

I also noticed that the following log entries appear when clicking the CTA button.

 1371-1371  LayerHistory            surfaceflinger                       I  world.mnetplus/com.applovinmaxexample.MainActivity$_8509#3351 Max (can't resolve refresh rate)

[alhiwatan]

@hongjae-eum, thank you for uploading the logs, and I apologize for the delay in getting back to you. Unfortunately, I couldn't find anything specific in the logs.
I wonder if the issue could be specific to Samsung devices. If you can access another Android device, could you try replicating the issue? I also have a Samsung tablet and was able to reproduce the issue on it.

[alhiwatan]

@hongjae-eum, we believe that the issue has been fixed in the v8.0.1. Could you check it out when you have a chance?