[$250] Unread DM from Managed Customer Not Surfacing in LHN (Only Visible via Search/Email Notification)

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number:
Reproducible in staging?: Needs Reproduction (Reproduction blocked as this requires DM from managed customer)
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @VictoriaExpensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Receive a DM from a managed customer
2. Ensure the chat appears in the LHN
3. Allow the customer to send a follow-up unread message
4. Observe LHN behavior
5. Check via email notification or search

Expected Result:

Any unread message should:
Cause the chat to surface/update in the LHN
Be clearly visible to the user without needing search or email
LHN ordering should reflect latest unread activity

Actual Result:

Initial message appears in LHN correctly
Subsequent unread replies:
Do not surface or move the chat in LHN
Chat only shows activity via:
Email notification
Search (chat appears bolded/unread)

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022057479701358803786
• Upwork Job ID: 2057479701358803786
• Last Price Increase: 2026-05-21

[MelvinBot]

Proposal

What is the root cause of that problem?

When a DM is created, it starts with notificationPreference: HIDDEN (Report/index.ts:2264). The preference is only changed from HIDDEN to ALWAYS client-side when the current user sends a message — via an optimistic update in addActions (Report/index.ts:908-913).

When the other user (the managed customer) sends subsequent messages, the client never updates the notification preference. If the server also fails to send an updated notificationPreference in the Onyx merge for the report, the report stays HIDDEN.

The LHN's shouldDisplayReportInLHN filters out hidden reports unless specific overrides apply. Critically, having unread messages is NOT one of the overrides — only draft comments, errors, being the focused report, system chat, pinned, requiresAttention (which for DMs requires an @mention), or own policy expense chat can override the hidden status. So the DM with new unread messages stays invisible in the LHN.

The initial message appearing correctly suggests the server unhides the report on first contact, but subsequent messages after the user has read the chat may not re-trigger this unhiding — or the preference gets reset to HIDDEN by a later Onyx merge.

What changes do you think we should make in order to solve the problem?

Add isUnread (without requiring a mention) as an override condition in the shouldOverrideHidden check in SidebarUtils.ts:321-329. Specifically, if a report isHidden but has unread messages (isUnread returns true), it should still be displayed in the LHN. This ensures that any incoming message — regardless of whether it contains a mention — surfaces the chat.

Additionally, the server-side behavior should be investigated to understand why the notificationPreference isn't being durably set to a non-hidden value after initial interaction with a DM. The client-side fix above is a safety net ensuring the LHN always surfaces reports with unread activity.

What alternative solutions did you explore? (Optional)

1. Change addActions to update notification preference on incoming messages too — this would require modifying the Pusher/server event handling to also optimistically update notificationPreference. However, this is more complex and doesn't address the fundamental issue that the LHN filtering logic silently hides reports with unread content.

2. Make requiresAttention return true for any unread DM — this would work but has side effects: it would also give unread DMs the green dot (GBR indicator) and float them to the pinned/GBR priority bucket, which is heavier than what's needed.

Supporting evidence

Key code locations:

• DM creation with HIDDEN preference: Report/index.ts:2264
• Preference only updated when current user sends: Report/index.ts:908-913
• Hidden check and override logic: SidebarUtils.ts:303-333
• isHiddenForCurrentUser treats null/empty as hidden: ReportUtils.ts:2220-2228
• requiresAttention only triggers on mentions for DMs: ReportUtils.ts:4225-4229

Likely related issue: Expensify/App#90434 — "Messages not highlighted as unread in LHN on web / real-time message updates not reflected" describes the same symptom pattern (intermittent failure to surface unread messages in LHN).

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[dilshodmackbook-sketch]

🚨 Edited by proposal-police: This proposal was edited at 2026-05-21 15:18:57 UTC.

Proposal

What is the root cause of that problem?

Every report rendered in the LHN is first filtered through shouldDisplayReportInLHN in SidebarUtils.ts. That function short-circuits on the hidden notification preference before it ever evaluates whether the report is unread:

https://github.com/Expensify/App/blob/main/src/libs/SidebarUtils.ts#L318-L333

const shouldOverrideHidden =
    !!draftComment ||
    hasErrorsOtherThanFailedReceipt ||
    isFocused ||
    isSystemChat ||
    !!report.isPinned ||
    requiresAttention ||
    (report.isOwnPolicyExpenseChat && !isReportArchived);

if (isHidden && !shouldOverrideHidden) {
    return {shouldDisplay: false};   // report dropped here — unread state never checked
}

shouldOverrideHidden covers drafts, errors, the focused report, system chats, pinned and GBR reports — but not unread. So a report whose notification preference resolves to hidden is removed from the LHN regardless of unread activity.

Crucially, getReportNotificationPreference returns hidden not only when the user explicitly hid the chat, but also as the default fallback whenever the current user's participant entry has no explicit notificationPreference:

https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L1887-L1893

A DM from a managed customer is exactly the kind of report that can land in Onyx with an incomplete current-user participant entry, so it resolves to hidden.

This also directly contradicts the documented intent of the LHN inclusion logic in reasonForReportToBeInOptionList — "All unread chats … will be shown" — which never gets a chance to run because shouldDisplayReportInLHN already bailed out:

https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.ts#L9631-L9638

Search builds its option list through shouldReportBeInOptionList directly and does not apply the shouldDisplayReportInLHN hidden gate — which is why the same chat still shows up bolded/unread in Search (and in the email notification) but is missing from the LHN, exactly as the screenshot shows.

What changes do you think we should make in order to solve the problem?

An unread report has new activity the user needs to see, so it should override the hidden gate — the same way a pinned report or a GBR already does. isUnread is already imported in SidebarUtils.ts, so this is a one-line addition to shouldOverrideHidden:

     const requiresAttention = reportAttributes?.[report?.reportID]?.requiresAttention;
     const isSystemChat = isSystemChatUtil(report);
+    const isReportUnread = isUnread(report, undefined, isReportArchived);
     const shouldOverrideHidden =
         !!draftComment ||
         hasErrorsOtherThanFailedReceipt ||
         isFocused ||
         isSystemChat ||
         !!report.isPinned ||
         // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
         requiresAttention ||
+        isReportUnread ||
         (report.isOwnPolicyExpenseChat && !isReportArchived);

With this, an unread DM passes the gate and reaches shouldReportBeInOptionList, which already returns IS_UNREAD in focus mode and DEFAULT in most-recent mode. Muted reports are unaffected — isHiddenForCurrentUser is only true for the hidden preference, never for mute, so the existing focus-mode !== MUTE check still governs muted chats. Once the chat is correctly included, the existing sortReportsToDisplayInLHN ordering (by lastVisibleActionCreated in most-recent mode) handles surfacing/moving it to the top on each follow-up message.

What alternative solutions did you explore? (Optional)

• Fix getReportNotificationPreference to not default a missing preference to hidden for DMs the user actively participates in. This addresses the upstream data gap, but the function is consumed app-wide (mute badges, notifications, settings), so changing its fallback risks wide, hard-to-test regressions — too broad for this bug.
• Apply the shouldDisplayReportInLHN hidden gate to Search too, to make LHN and Search "consistent." Rejected — that's the wrong direction: it would also hide the unread chat from Search, removing the only place the user can currently find it.
• Add the unread override only in focus (#focus/GSD) mode. Rejected — the chat is missing in most-recent mode as well, and an unread message should surface a chat regardless of priority mode, which is what the issue's expected result asks for.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022057479701358803786

[github-actions]

⚠️ @dilshodmackbook-sketch Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

[mukhrr]

Proposal

What is the root cause of that problem?

When an LHN row is evaluated in shouldDisplayReportInLHN, a chat whose participant notificationPreference is HIDDEN is filtered out unless one of the shouldOverrideHidden reasons applies (draft, error, focus, system chat, pin, requiresAttention, or own policy expense chat):

App/src/libs/SidebarUtils.ts

Lines 319 to 333 in e3b5200

	const requiresAttention = reportAttributes?.[report?.reportID]?.requiresAttention;
	const isSystemChat = isSystemChatUtil(report);
	const shouldOverrideHidden =
	!!draftComment ||
	hasErrorsOtherThanFailedReceipt ||
	isFocused ||
	isSystemChat ||
	!!report.isPinned ||
	// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
	requiresAttention ||
	(report.isOwnPolicyExpenseChat && !isReportArchived);
	if (isHidden && !shouldOverrideHidden) {
	return {shouldDisplay: false};
	}

requiresAttention is derived from getReasonAndReportActionThatRequiresAttention, which only treats unread chats as attention-worthy when there is an explicit @mention:

App/src/libs/ReportUtils.ts

Lines 4221 to 4225 in e3b5200

	if (isUnreadWithMention(optionOrReport)) {
	return {
	reason: CONST.REQUIRES_ATTENTION_REASONS.IS_UNREAD_WITH_MENTION,
	};
	}

For a DM from a managed customer, the recipient's participant entry can be created without a notificationPreference, which defaults to HIDDEN:

App/src/libs/ReportUtils.ts

Lines 1883 to 1889 in e3b5200

	function getReportNotificationPreference(report: OnyxEntry<Report>): ValueOf<typeof CONST.REPORT.NOTIFICATION_PREFERENCE> {
	const participant = deprecatedCurrentUserAccountID ? report?.participants?.[deprecatedCurrentUserAccountID] : undefined;
	// Empty notification preference should return `hidden`
	// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
	return participant?.notificationPreference || CONST.REPORT.NOTIFICATION_PREFERENCE.HIDDEN;
	}

So the first inbound message can briefly surface the chat (creation/onboarding side-effects), but every subsequent reply lands on a report whose isHiddenForCurrentUser(report) === true. Because plain unread 1:1 messages don't carry a mention, requiresAttention stays false, none of the other override flags fire, and shouldDisplayReportInLHN returns {shouldDisplay: false} — the chat is dropped from the LHN cache and categorizeReportsForLHN/sortReportsToDisplayInLHN never see it again. Search and the email notifier compute "unread" directly from lastReadTime < lastVisibleActionCreated, so they keep flagging the chat as unread, which is exactly the asymmetry the reporter observed.

What changes do you think we should make in order to solve the problem?

I think we should let an unread DM/group chat override the HIDDEN notification preference for LHN display. The narrowest place to do that is inside shouldDisplayReportInLHN — treat isUnread (without requiring a mention) as another shouldOverrideHidden reason, scoped to 1:1 DMs and group chats so we don't accidentally re-surface explicitly hidden rooms/policy chats.

In src/libs/SidebarUtils.ts (around L321):

-    const shouldOverrideHidden =
-        !!draftComment ||
-        hasErrorsOtherThanFailedReceipt ||
-        isFocused ||
-        isSystemChat ||
-        !!report.isPinned ||
-        // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
-        requiresAttention ||
-        (report.isOwnPolicyExpenseChat && !isReportArchived);
+    const isUnreadOneOnOneOrGroup =
+        (isOneOnOneChat(report) || isGroupChat(report)) &&
+        isUnread(report, undefined, isReportArchived) &&
+        getReportNotificationPreference(report) !== CONST.REPORT.NOTIFICATION_PREFERENCE.MUTE;
+
+    const shouldOverrideHidden =
+        !!draftComment ||
+        hasErrorsOtherThanFailedReceipt ||
+        isFocused ||
+        isSystemChat ||
+        !!report.isPinned ||
+        // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
+        requiresAttention ||
+        isUnreadOneOnOneOrGroup ||
+        (report.isOwnPolicyExpenseChat && !isReportArchived);

isOneOnOneChat, isGroupChat, getReportNotificationPreference, and isUnread are already imported from ReportUtils in this file. The MUTE check preserves the user's explicit "stop notifying me" choice — only chats that are passively HIDDEN (the managed-customer default) get re-surfaced when there is genuinely new activity.

Two supporting touches:

• Add the same isUnreadOneOnOneOrGroup short-circuit before the early return null paths in reasonForReportToBeInOptionList (src/libs/ReportUtils.ts around L9626 / the focus-mode branch) so search and option lists agree with the LHN.
• Add a Jest case in tests/unit/SidebarFilterTest.ts covering "1:1 DM with notificationPreference: HIDDEN and lastVisibleActionCreated > lastReadTime shows in LHN".

What alternative solutions did you explore?

• Promote plain isUnread to requiresAttention inside getReasonAndReportActionThatRequiresAttention. Rejected — requiresAttention also drives the GBR/green-dot pinned-and-GBR bucket in categorizeReportsForLHN, so every passively unread chat would jump to the top of the LHN and grow a green dot. The scope of that change is much wider than the bug.
• Backend fix: stop creating managed-customer DM participants with an empty notificationPreference. That's the cleanest root-cause fix, but it leaves every existing affected report stuck on the client until the participant record is rewritten, and we can't ship it from this repo. The LHN guard above also protects users whose participants are already in this state.

[abbasifaizan70]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a managed customer sends a DM, the initial message appears correctly in the LHN. However, subsequent unread replies from the customer do not surface or move the chat in the LHN. The chat only shows activity via email notification or search (where it appears bolded/unread). Any unread message should cause the chat to surface/update in the LHN and be clearly visible to the user without needing search or email.

What is the root cause of that problem?

The root cause is that reports with a HIDDEN notification preference are filtered out in shouldDisplayReportInLHN before the unread check can surface them.

When a managed customer first sends a DM, the chat is created with NOTIFICATION_PREFERENCE.ALWAYS, so it appears correctly. After the user interacts or navigates away, the preference can change to HIDDEN. When the customer sends follow-up messages, the report gets filtered out early because the shouldOverrideHidden condition does not include an unread check.

The isHidden check happens here, determining if the report has a HIDDEN notification preference:

App/src/libs/SidebarUtils.ts

Line 303 in 08ffe4a

const isHidden = isHiddenForCurrentUser(report);

The shouldOverrideHidden condition includes draft comments, errors, focused state, system chats, pinned reports, and attention-requiring reports, but does not check for unread state:

App/src/libs/SidebarUtils.ts

Lines 321 to 329 in 08ffe4a

	const shouldOverrideHidden =
	!!draftComment ||
	hasErrorsOtherThanFailedReceipt ||
	isFocused ||
	isSystemChat ||
	!!report.isPinned ||
	// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
	requiresAttention ||
	(report.isOwnPolicyExpenseChat && !isReportArchived);

When a report is hidden and none of the override conditions are met, it gets filtered out before reaching the unread handling logic:

App/src/libs/SidebarUtils.ts

Lines 331 to 333 in 08ffe4a

	if (isHidden && !shouldOverrideHidden) {
	return {shouldDisplay: false};
	}

In contrast, GSD (Focus) mode has explicit unread handling in reasonForReportToBeInOptionList, but this code is never reached for hidden reports in default mode because they are filtered out earlier:

App/src/libs/ReportUtils.ts

Lines 9631 to 9637 in 08ffe4a

	// All unread chats (even archived ones) in GSD mode will be shown. This is because GSD mode is specifically for focusing the user on the most relevant chats, primarily, the unread ones
	if (isInFocusMode) {
	const oneTransactionThreadReportID = getOneTransactionThreadReportID(report, chatReport, currentReportActions);
	const oneTransactionThreadReport = deprecatedAllReports?.[`${ONYXKEYS.COLLECTION.REPORT}${oneTransactionThreadReportID}`];
	return isUnread(report, oneTransactionThreadReport, isReportArchived) && getReportNotificationPreference(report) !== CONST.REPORT.NOTIFICATION_PREFERENCE.MUTE
	? CONST.REPORT_IN_LHN_REASONS.IS_UNREAD
	: null;

What changes do you think we should make in order to solve the problem?

Add an unread check to the shouldOverrideHidden condition so that reports with unread messages surface in the LHN even if they have a HIDDEN notification preference.

File: src/libs/SidebarUtils.ts

App/src/libs/SidebarUtils.ts

Lines 318 to 333 in 08ffe4a

	// Check if report should override hidden status
	const requiresAttention = reportAttributes?.[report?.reportID]?.requiresAttention;
	const isSystemChat = isSystemChatUtil(report);
	const shouldOverrideHidden =
	!!draftComment ||
	hasErrorsOtherThanFailedReceipt ||
	isFocused ||
	isSystemChat ||
	!!report.isPinned ||
	// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
	requiresAttention ||
	(report.isOwnPolicyExpenseChat && !isReportArchived);
	if (isHidden && !shouldOverrideHidden) {
	return {shouldDisplay: false};
	}

    // Check if report should override hidden status
    const requiresAttention = reportAttributes?.[report?.reportID]?.requiresAttention;
    const isSystemChat = isSystemChatUtil(report);
    const oneTransactionThreadReportID = getOneTransactionThreadReportID(report, chatReport, allReportActions?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.reportID}`]);
    const oneTransactionThreadReport = reports?.[`${ONYXKEYS.COLLECTION.REPORT}${oneTransactionThreadReportID}`];
    const reportIsUnread = isUnread(report, oneTransactionThreadReport, isReportArchived);
    const shouldOverrideHidden =
        !!draftComment ||
        hasErrorsOtherThanFailedReceipt ||
        isFocused ||
        isSystemChat ||
        !!report.isPinned ||
        // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
        requiresAttention ||
        (report.isOwnPolicyExpenseChat && !isReportArchived) ||
        reportIsUnread;

    if (isHidden && !shouldOverrideHidden) {
        return {shouldDisplay: false};
    }

Add import for getOneTransactionThreadReportID from ReportActionsUtils:

App/src/libs/SidebarUtils.ts

Lines 38 to 141 in 08ffe4a

	import {
	getActionableCard3DSTransactionApprovalMessage,
	getActionableCardFraudAlertResolutionMessage,
	getAddedApprovalRuleMessage,
	getAddedBudgetMessage,
	getAddedCardFeedMessage,
	getAddedConnectionMessage,
	getAssignedCompanyCardMessage,
	getAutoPayApprovedReportsEnabledMessage,
	getAutoReimbursementMessage,
	getCardIssuedMessage,
	getChangedApproverActionMessage,
	getCompanyAddressUpdateMessage,
	getCompanyCardConnectionBrokenMessage,
	getCurrencyDefaultTaxUpdateMessage,
	getCustomTaxNameUpdateMessage,
	getDefaultApproverUpdateMessage,
	getDeletedApprovalRuleMessage,
	getDeletedBudgetMessage,
	getForeignCurrencyDefaultTaxUpdateMessage,
	getForwardsToUpdateMessage,
	getIntegrationSyncFailedMessage,
	getInvoiceCompanyNameUpdateMessage,
	getInvoiceCompanyWebsiteUpdateMessage,
	getIOUReportIDFromReportActionPreview,
	getLastVisibleMessage,
	getMessageOfOldDotReportAction,
	getOriginalMessage,
	getPlaidBalanceFailureMessage,
	getPolicyChangeLogAddEmployeeMessage,
	getPolicyChangeLogDefaultBillableMessage,
	getPolicyChangeLogDefaultReimbursableMessage,
	getPolicyChangeLogDefaultTitleEnforcedMessage,
	getPolicyChangeLogDeleteMemberMessage,
	getPolicyChangeLogEmployeeLeftMessage,
	getPolicyChangeLogMaxExpenseAgeMessage,
	getPolicyChangeLogMaxExpenseAmountMessage,
	getPolicyChangeLogMaxExpenseAmountNoItemizedReceiptMessage,
	getPolicyChangeLogMaxExpenseAmountNoReceiptMessage,
	getPolicyChangeLogUpdateEmployee,
	getReimburserUpdateMessage,
	getRemovedCardFeedMessage,
	getRemovedConnectionMessage,
	getRenamedAction,
	getRenamedCardFeedMessage,
	getReportAction,
	getReportActionActorAccountID,
	getReportActionMessageText,
	getRequireCompanyCardsEnabledMessage,
	getRoomAvatarUpdatedMessage,
	getSetAutoJoinMessage,
	getSettlementAccountLockedMessage,
	getSubmitsToUpdateMessage,
	getTagListNameUpdatedMessage,
	getTagListUpdatedMessage,
	getTagListUpdatedRequiredMessage,
	getTravelUpdateMessage,
	getUnassignedCompanyCardMessage,
	getUpdateACHAccountMessage,
	getUpdatedApprovalRuleMessage,
	getUpdatedAuditRateMessage,
	getUpdatedAutoHarvestingMessage,
	getUpdatedBudgetMessage,
	getUpdatedCardFeedLiabilityMessage,
	getUpdatedCardFeedStatementPeriodMessage,
	getUpdatedDefaultTitleMessage,
	getUpdatedIndividualBudgetNotificationMessage,
	getUpdatedManualApprovalThresholdMessage,
	getUpdatedOwnershipMessage,
	getUpdatedProhibitedExpensesMessage,
	getUpdatedReimbursementChoiceMessage,
	getUpdatedSharedBudgetNotificationMessage,
	getUpdatedTimeEnabledMessage,
	getUpdatedTimeRateMessage,
	getUpdateRoomDescriptionMessage,
	getWorkspaceAttendeeTrackingUpdateMessage,
	getWorkspaceCategoriesUpdatedMessage,
	getWorkspaceCategoryUpdateMessage,
	getWorkspaceCurrencyUpdateMessage,
	getWorkspaceCustomUnitRateAddedMessage,
	getWorkspaceCustomUnitRateDeletedMessage,
	getWorkspaceCustomUnitRateImportedMessage,
	getWorkspaceCustomUnitRateUpdatedMessage,
	getWorkspaceCustomUnitSubRateDeletedMessage,
	getWorkspaceCustomUnitSubRateUpdatedMessage,
	getWorkspaceCustomUnitUpdatedMessage,
	getWorkspaceDescriptionUpdatedMessage,
	getWorkspaceFeatureEnabledMessage,
	getWorkspaceFrequencyUpdateMessage,
	getWorkspaceReimbursementUpdateMessage,
	getWorkspaceReportFieldAddMessage,
	getWorkspaceReportFieldDeleteMessage,
	getWorkspaceReportFieldUpdateMessage,
	getWorkspaceTagUpdateMessage,
	getWorkspaceTaxUpdateMessage,
	getWorkspaceUpdateFieldMessage,
	isActionOfType,
	isCardIssuedAction,
	isInviteOrRemovedAction,
	isOldDotReportAction,
	isRenamedAction,
	isTagModificationAction,
	isTaskAction,
	} from './ReportActionsUtils';

Add a module-level variable to access report actions (similar to how ReportUtils.ts does it):

let allReportActions: OnyxCollection<ReportActions> = {};
Onyx.connect({
    key: ONYXKEYS.COLLECTION.REPORT_ACTIONS,
    waitForCollectionCallback: true,
    callback: (value) => {
        allReportActions = value;
    },
});

[github-actions]

⚠️ @abbasifaizan70 Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.