IssueTracker

Project: platform/frameworks/support
Branch: androidx-main

commit f6213155bca580ad31fdae5476bd9cae18b10c70
Author: Jeremy Woods <jbwoods@google.com>
Date:   Wed May 25 15:32:22 2022

    Fix namespacing for Navigation SafeArgs in AGP
   
    There is an issue with the new namespace support in Navigation Safe Args
    which if there is an applicationIdSuffix and a namespace with no package
    name provided in an AndroidManifest, or there is a suffix with differing
    namespace and package name in AndroidManifest, the resource directory
    package isn't properly generated in the SafeArgs class.
   
    Namespace does not take into account applicationIdSuffix and SafeArgs
    still needs to since the generated classes need to be in the same package
    as the classes they are being generated from if they use relatives paths
    in the xml.
   
    This means the following:
    1. We always need to use the applicationId to get the proper location of
       the generated file.
    2. If a namespace is available, we need to use that to identify the
       location of the R resource class.
   
    RelNote: "`Navigation SafeArgs` will no longer crash when using an
    `applicationIdSuffix` and namespace with either no applicationId
    present, or when the applicationId and namespace differ."
    Test: modified safeargs test
    Bug: 233119646
   
    Change-Id: I754b1fffe44bdb142ae818187cad6cd7fdc9080a

M       navigation/navigation-safe-args-gradle-plugin/src/test/kotlin/androidx/navigation/safeargs/gradle/BasePluginTest.kt
M       navigation/navigation-safe-args-gradle-plugin/src/main/kotlin/androidx/navigation/safeargs/gradle/SafeArgsPlugin.kt
M       navigation/navigation-safe-args-gradle-plugin/src/test/kotlin/androidx/navigation/safeargs/gradle/KotlinPluginTest.kt

https://android-review.googlesource.com/2108694

thanks, 2.5.0-rc02 fixed the issue