I've two application modules, app_a_app and app_b_app. And feature modules like app_a_payment and app_b_payment. These specific modules inherit from an common scope module like payment.

In specific feature modules (by app), always the activity have the same name and the same EntryFlowNav like PayersActivity.

So my module router do the maginc (with this cool library) calling the right path. Like start(FEATURE_X) inside a extension function like openFeatureX().

When I'm running the app, the entrymap generated by library it's mixing paths from feature modules from other application module.

E.g.:

[1] br.com.app_a.ScreenCool [2] br.com.app_b.ScreenCool

I'm seeing references/paths in wrong application, causing ActivityNotFoundException.

Can I handle multiples flownav.main.module with this library? I've multiple applications modules in my scenario, it's a kind of white label application.

We're using https://github.com/Tulioh/SweetFactory to handle multi module navigation, it's working well but unhappy this processors is not incremental.

java.lang.RuntimeException: Unable to create application br.X.X.App: kotlin.UninitializedPropertyAccessException: lateinit property entryMap has not been initialized [...] Caused by: kotlin.UninitializedPropertyAccessException: lateinit property entryMap has not been initialized

My modules:

• app_x_app: contains application class annotated with @FlowNavMain and started with FlowNavApp.start(getEntryMap()) in onCreate method. Use kapt processor and implementation of annotation.

• app_x_login: contains login activity annotated with @EntryFlowNav(NavigationKeys.FEATURE_LOGIN). Use kapt processor and implementation of annotation.

• router: contains a extension function to open login activity. Use kapt processor, implementation of annotation and router implementation (as 'api') .

fun BaseActivity.openLoginWithoutHistory() {
    start(
        FEATURE_LOGIN,
        listOf(
            Intent.FLAG_ACTIVITY_NO_ANIMATION,
            Intent.FLAG_ACTIVITY_NEW_TASK,
            Intent.FLAG_ACTIVITY_CLEAR_TASK
        )
    )
}

The big vision is:

• app_x_app
• • app_x_login
• • router

In gradle.properties:

flownav.main.module=app_x_app

What am I missing?

This PR add support to multiples application module in some project #14.

Add to gradle.peoperties yours application modules using ,.

flownav.main.module=appmodule1,appmodule2,appmodule3

New application module was added on sample.

If other module is used as application module (instead of theapp module), now is supported by FlowNav with the property flownav.main.module on gradle.properties file.

This PR include changes for add native support to Fragment (before only with the Navigation Component). Also, some improvements was added:

• Better FlowNav setup
• Add flags to navigation using Intents
• Remove EntryFragmentFlowNav extension and add actionId to EntryFlowNav