Allow manually marking screen boundaries

[mxalbert1996]

Is your feature request related to a problem? Please describe.

According to the doc, screen boundaries are only detected when 1) Activity.onResume() is called or 2) a new view event is fired.
We are migrating our app from multiple-activity to single-activity with navigation compose. As we are only firing view events on some screens, screen boundary is not detected when we transition to a screen without a view event, and the popup is not dismissed.

Describe the solution you'd like

Provide an API such as KarteApp.markScreenBoundary() to allow manually marking screen boundaries.
Once this API is provided, we can do something like this:

navController.currentBackStackEntryFlow.collect { KarteApp.markScreenBoundary() }

Describe alternatives you've considered

We considered using InAppMessaging.dismiss(), but doing that essentially makes the option "Do not control display and always display" unusable.

If there is any solution other than adding a view event for every screen, please let me know!

[t5kz]

@mxalbert1996 Thank you for contacting us. We will share your comments with the SDK development team as feedback.

The issue you're currently facing may vary depending on your individual environment, so if you need more specific support, we recommend contacting a PLAID representative or chat support on the admin console.

Also, as a general note, the current recommended format for explicitly recognizing screen boundaries is to use the view event.
This is to standardize the behavior of our product, both on websites (where a view event is automatically sent when the page loads and display control is performed accordingly) and native apps.

Also, as you said, "As we are only firing view events on some screens," it appears that in this case, the firing of the view event is restricted for some reason. However, the recommended format is to fire the view event on all screens.

There are likely implementation issues due to various circumstances, but questions about implementation in individual native apps often cannot be resolved through issue discussions.
Again, as mentioned above, we recommend contacting a PLAID representative or via chat support on the admin console.