[GH-ISSUE #739] [suggestion] fix file picker & Local Notification Feature #662

Closed
opened 2026-03-03 15:35:23 +03:00 by kerem · 0 comments
Owner

Originally created by @kidkunlazy on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/739

Hello, I have an app that used to run properly in earlier versions with the Fix File Picker & Local Notification feature enabled. However, in the updated version, when checking to see if the Bundle ID has been modified, the NSLog indicates a mismatch between the application's bundle identifier and SecurityGuardSDK's jpg file (yw_1222). The Fix File Picker & Local Notification feature appears to be temporarily replacing the sub-app's Bundle ID with the LiveContainer main app's own Bundle ID. This new version of the app has built-in security checks, and upon startup, it checks to see if its Bundle ID matches the one it compiled with. The LiveContainer causes the new version app to detect the identity tampering and refuse to run. Is there a way to enable the sub-app to see the LiveContainer's fake Bundle ID at the iOS system level (e.g., when requesting notification permissions or calling the file picker), allowing the sub-app to obtain permissions normally? During self-checks, the sub-app will detect its native Bundle ID.

Originally created by @kidkunlazy on GitHub (Aug 7, 2025). Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/739 Hello, I have an app that used to run properly in earlier versions with the Fix File Picker & Local Notification feature enabled. However, in the updated version, when checking to see if the Bundle ID has been modified, the NSLog indicates a mismatch between the application's bundle identifier and SecurityGuardSDK's jpg file (yw_1222). The Fix File Picker & Local Notification feature appears to be temporarily replacing the sub-app's Bundle ID with the LiveContainer main app's own Bundle ID. This new version of the app has built-in security checks, and upon startup, it checks to see if its Bundle ID matches the one it compiled with. The LiveContainer causes the new version app to detect the identity tampering and refuse to run. Is there a way to enable the sub-app to see the LiveContainer's fake Bundle ID at the iOS system level (e.g., when requesting notification permissions or calling the file picker), allowing the sub-app to obtain permissions normally? During self-checks, the sub-app will detect its native Bundle ID.
kerem closed this issue 2026-03-03 15:35:24 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LiveContainer#662
No description provided.