IssueTracker

Please include a sample project that reproduces your issue.

Sample project attached. Just add to plain project this dependencies allow to reproduce.

def emoji2_version = "1.1.0-beta01"
implementation "androidx.emoji2:emoji2:$emoji2_version"

def lifecycle_version = "2.5.0-alpha01"
implementation "androidx.lifecycle:lifecycle-process:$lifecycle_version"

The reason may be related to this change, which check itself before it is initialized. Use 2.4.0 of lifecycle-process as workaround.

Yes, this is due to this change, as well as the fact that EmojiCompatInitializer has a ProcessLifecycleInitializer as a dependency and also re-calls it, but in manual mode.

ProcessLifecycleInitializer is expected to already be initialized (via the manifest provider for App Startup) by the time that code runs - App Startup shouldn't be calling create if that component has already been initialized, hence you shouldn't get any exception. We'll take a look on where things are breaking down though.

Thanks for the answer.

As I understand EmojiCompatInitializer has ProcessLifecycleInitializer as a dependency. That is mean, the ProcessLifecycleInitializer must be executed before the EmojiCompatInitializer, which in its create method calls the delayUntilFirstResume method, which in turn calls the ProcessLifecycleInitializer via appInitializer.initializeComponent(ProcessLifecycleInitializer.class)

Maybe it would be more correct to create a bug in emoji-2, but let it be here.

This issue isn't related to emoji2, it could be reproduced easily with the lifecycle-process (2.4.0 -> 2.5.0-alpha01) only.

This has been fixed internally and will be released in the Lifecycle 2.5.0-alpha02 release.

When will start-up 1.1.1 release?

It should be out before the end of the week.

I guess the release that addresses this is actually: androidx.compose.material:material-navigation:1.7.0-alpha04

As #13 said, we are missing this for Material3 bottom sheets. I see that there's another issue tracking that here: https://issuetracker.google.com/issues/328949006

Some guidance about usage would be very welcome. I get java.lang.IllegalStateException: Could not find Navigator with name "bottomSheet". You must call NavController.addNavigator() for each navigation type. crash and can't find any proper example of this new extension usage:

                Scaffold(
                    bottomBar = {...}
                      
                ) { innerPadding ->

                    NavHost(
                        navController,
                        startDestination = "explore_graph",
                        Modifier.fillMaxSize()
                    ) {
                        // nested graphs

                        bottomSheet("profile_bottom_sheet") { // CRASHES
                            Text("Bottom Sheet", Modifier.padding(16.dp))
                        }
                    }
                }
            }
        }
    }
}

I use androidx.compose.material:material-navigation:1.7.0-beta01, but my project is material3, could it be the reason?

Re comment#15 - Material Navigation works similarly to Accompanist, whose docs explain how to use it, including these two lines:

val bottomSheetNavigator = rememberBottomSheetNavigator()
val navController = rememberNavController(bottomSheetNavigator)

If you don't use those lines, you'd get that error message.