Discord manifest script appends all found manifest files instead of only the Discord one

[ToNIX-]

I observed that the Discord manifest script appends all found manifest files instead of only parsing the one that's related to Discord.

Here's the log of the "processed files list" :

For discordmanifest module:

3 files for regex */mobile/Containers/Data/Application/*/Documents/RCTAsyncLocalStorage_V1/manifest.json located at:

        C:\Temp\ileapp\iLEAPP_Reports_2025-11-17_Monday_112337\data\private\var\mobile\Containers\Data\Application\27A0920F-1D77-4DE3-99BB-C9B89AF575E3\Documents\RCTAsyncLocalStorage_V1\manifest.json

        C:\Temp\ileapp\iLEAPP_Reports_2025-11-17_Monday_112337\data\private\var\mobile\Containers\Data\Application\C56E9C42-C4AB-463A-9B12-A1C8019EE65D\Documents\RCTAsyncLocalStorage_V1\manifest.json

        C:\Temp\ileapp\iLEAPP_Reports_2025-11-17_Monday_112337\data\private\var\mobile\Containers\Data\Application\15B02AE7-7243-41F5-906F-33335516A5DB\Documents\RCTAsyncLocalStorage_V1\manifest.json

App ID 27A0920F-1D77-4DE3-99BB-C9B89AF575E3 corresponds to the Amazon app
App ID C56E9C42-C4AB-463A-9B12-A1C8019EE65D corresponds to the Discord app
App ID 15B02AE7-7243-41F5-906F-33335516A5DB corresponds to the Facebook app

The "Discord Manifest report" heading shows that the manifest was located at the Facebook app path instead of the Discord app:

C:\Temp\ileapp\iLEAPP_Reports_2025-11-17_Monday_112337\data\private\var\mobile\Containers\Data\Application\15B02AE7-7243-41F5-906F-33335516A5DB\Documents\RCTAsyncLocalStorage_V1\manifest.json

The "Discord Manifest report" itself shows all 3 found manifest files parsed and appended together, instead of validating which one belongs to Discord and parsing only this one.

[JamesHabben]

It seems that this module should be renamed since that manifest file is related to react native async storage and is not discord specific. These manifest files will contain whatever the app developers decide to put there.

I also saw some notes in searching that developers have the option of storing this manifest file in user accessible documents folder or in the non-accessible application support folder. The current search pattern will not return those stored in app support.

The module should be updated to have a found file path column to show which manifest file each of the values were extracted from. The path can then be used by the examiner to determine which app each value is associated with by reviewing other artifact results to resolve the GUID values to app names.

In a future state when we get the core functionality in to parse app info, we can add a column to directly identify which app stored each of the values, but we aren't there yet.