InApp messages transaction too Large about exponea-android-sdk HOT 5 CLOSED

Hi @cernfr1993 thank you for your reporting, we are still investigating a case.
Main problem here may be that in case of large content of InApp is sending to particular part of code (opening InApp with Activity/Fragment), system is killing it to some limitations -> this is result of our internal analysis.
Please check if you are using some really large InApp messages, especially builded by HTML editor, check for large images there or so.

from exponea-android-sdk.

Thank you for your response.
We do not use HTML builder in our inAppMessages and image has only 94 kB. I spouse image is not causing the problem. We also noticed this type of problem:

Caused by java.io.NotSerializableException
pn.b
java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1240)

I hope it will help you.

Thank you.

from exponea-android-sdk.

Hi @cernfr1993 thank you for more info.
Unfortunatelly we are not able to reproduce this error. We tried large HTML inapps, large images and very long content in model InApps, but with no luck. Please do you have some stacktraces with SDK lines? Because we are not able to detect problem directly.
Stacktrace readiness is also needed for second problem with obfuscated 'pn.c' class. Is it SDK related?
If you want to share some code with us but is sensitive, please ask our support. Thank you

from exponea-android-sdk.

Hi @adam1929 i was able to find more information about relation between InAppMessages and TransactionTooLarge exception.

2022-12-13 11:47:32.984 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I Requesting to show in-app message for event type page_visit
2022-12-13 11:47:32.984 30741-30968 StandaloneCoroutine com.pragonauts.notino.debug I In-app message data preloaded, picking a message to display
2022-12-13 11:47:32.986 30741-31413 InAppMessageManagerImpl com.pragonauts.notino.debug I Requesting to show in-app message for event type page_visit
2022-12-13 11:47:32.987 30741-31413 StandaloneCoroutine com.pragonauts.notino.debug I In-app message data preloaded, picking a message to display
2022-12-13 11:47:32.987 30741-31413 InAppMessageManagerImpl com.pragonauts.notino.debug I Picking in-app message for eventType page_visit. 0 messages available: [].
2022-12-13 11:47:32.987 30741-31413 InAppMessageManagerImpl com.pragonauts.notino.debug I 0 messages available after filtering. Picking highest priority message.
2022-12-13 11:47:32.987 30741-31413 InAppMessageManagerImpl com.pragonauts.notino.debug I Got 0 messages with highest priority. []
2022-12-13 11:47:32.988 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I Picking in-app message for eventType page_visit. 0 messages available: [].
2022-12-13 11:47:32.988 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I 0 messages available after filtering. Picking highest priority message.
2022-12-13 11:47:32.988 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I Got 0 messages with highest priority. []
2022-12-13 11:47:32.991 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Requesting to show in-app message for event type page_visit
2022-12-13 11:47:32.991 30741-31410 StandaloneCoroutine com.pragonauts.notino.debug I In-app message data preloaded, picking a message to display
2022-12-13 11:47:32.991 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Picking in-app message for eventType page_visit. 0 messages available: [].
2022-12-13 11:47:32.991 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I 0 messages available after filtering. Picking highest priority message.
2022-12-13 11:47:32.991 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Got 0 messages with highest priority. []
2022-12-13 11:47:32.998 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I Requesting to show in-app message for event type page_visit
2022-12-13 11:47:32.999 30741-30968 StandaloneCoroutine com.pragonauts.notino.debug I In-app message data preloaded, picking a message to display
2022-12-13 11:47:32.999 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I Picking in-app message for eventType page_visit. 0 messages available: [].
2022-12-13 11:47:32.999 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I 0 messages available after filtering. Picking highest priority message.
2022-12-13 11:47:32.999 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I Got 0 messages with highest priority. []
2022-12-13 11:47:33.007 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Requesting to show in-app message for event type page_visit
2022-12-13 11:47:33.008 30741-31410 StandaloneCoroutine com.pragonauts.notino.debug I In-app message data preloaded, picking a message to display
2022-12-13 11:47:33.008 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Picking in-app message for eventType page_visit. 0 messages available: [].
2022-12-13 11:47:33.008 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I 0 messages available after filtering. Picking highest priority message.
2022-12-13 11:47:33.008 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Got 0 messages with highest priority. []
2022-12-13 11:47:33.016 30741-30968 InAppMessageManagerImpl com.pragonauts.notino.debug I Requesting to show in-app message for event type page_visit
2022-12-13 11:47:33.016 30741-31410 StandaloneCoroutine com.pragonauts.notino.debug I In-app message data preloaded, picking a message to display
2022-12-13 11:47:33.017 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Picking in-app message for eventType page_visit. 0 messages available: [].
2022-12-13 11:47:33.017 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I 0 messages available after filtering. Picking highest priority message.
2022-12-13 11:47:33.017 30741-31410 InAppMessageManagerImpl com.pragonauts.notino.debug I Got 0 messages with highest priority. []

This problems happens when event page_visit is logged to SDK. Could you please check why Exponea SDK is trying to show InAppMessage even thought we do not have any InAppMessages active (only one InAppMessage is started but is outside of active time range).
Beside that our app tries to open Activity with event page_visit multiple times (we do not why its happening) and its causing app to crash. (Too many activities on backstack).

Thank you.

from exponea-android-sdk.

Hi @cernfr1993 I'm not seeing any relation of Exception and InApps from your log.
Log is saying that InAppMessageManager is searching for InApp for 'page_visit' event, and that is done on every page_visit event track - that is correct.
As you can see in logs there are messages such as '0 messages available after filtering' etc. This means obviously that there are no messages to be shown, so it don't try to open any Activity from SDK (for InApp showing purpose).

Honestly, there are some possible improvements in SDK for this case of high frequency tracking, but I doubt that change will help == SDK is using daemon threads for showing InApp message and these daemon threads holds some runtime resources. They need to. But chaining them is not a solution in this case, because multiple events tracking will hold that chain for no reason here and other InApp showing will be delayed too much.
Please try to find out why 'page_visit' is tracking so often and reduce that.

from exponea-android-sdk.