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.

It seems this has been included in the 2.4.0-alpha01 release.

But is there any additional setup required besides updating the navigation dependencies? With the following dependencies on my project

object Navigation {
    private const val version = "2.4.0-alpha01"
    const val compose = "androidx.navigation:navigation-compose:$version"
    const val fragment = "androidx.navigation:navigation-fragment-ktx:$version"
    const val safeArgsPlugin = "androidx.navigation:navigation-safe-args-gradle-plugin:$version"
    const val ui = "androidx.navigation:navigation-ui-ktx:$version"
}

my safeargs don't generate fromSavedStateHandle().

fromBundle() is still the only auto-complete suggestion.

FooFragmentArgs.fromSavedStateHandle(savedStateHandle) is an unresolved reference in my ViewModel.

Re #13, #14 - please upgrade to the latest version of Android Studio and file a bug against Android Studio if you are still not seeing this method in the Studio generated light classes.

I'm using Arctic Fox | 2020.3.1 Canary 9. I've just updated Navigation to 2.4.0-alpha02 and still seeing the bug, so I've filed a bug against AS. https://issuetracker.google.com/issues/189966590

As mentioned in the linked issue, manually downloading the latest version of Android Studio Preview fixes the issue