Nuclei Category Opening as a seperate app in recents

Nuclei Category Opening as a seperate app in recents

When partner app uses multiple stack architecture, they might face this issue where the nuclei category appears as a separate app in recents of the device.

This issue arises when the nucleiTaskId passed in build.gradle is not the same as task Affinity of the application of the partner app or not present itself.

There are two cases possible:

1. When the partner app is setting Task Affinity explicitly for their application.

Eg. In partner`s AndroidManifest.xml

 <application
        android:name="in.nuclei.sampleapp.SampleApplication"
        android:taskAffinity="com.nuclei.sampleApp"
        ...>
 </application>

In such a case, the partner should pass the same value as their Task Affinity for nucleiTaskId in build.gradle

Eg. In partner`s app level build.gradle

android {
   ...
   defaultConfig {
       ...
       manifestPlaceholders = [nucleiTaskId: "com.nuclei.sampleApp"]
       ...
   }
   
}

2. When the partner app is not setting Task Affinity explicitly for their application.

In such case, the partner should pass applicationId as nucleiTaskId

Eg. In partner`s app level build.gradle

android {
   ...
   defaultConfig {
       ...
       manifestPlaceholders = [nucleiTaskId: applicationId]
       ...
   }
   
}