[GH-ISSUE #1154] keychain-access-groups correct: NO — Instagram suggests account from another container #1013

New issue

Closed

opened 2026-03-03 15:37:59 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 15:37:59 +03:00

Owner

Originally created by @olejenek500-web on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/1154

Description
When running two Instagram containers with "Isolate App Group" enabled, the second container still shows "Continue as [account]" on the login screen — suggesting the account logged in from the first container.
In Settings → JITL-Less Mode Diagnose → Entitlement File, keychain-access-groups shows Correct: NO, which means keychain isolation is not working between containers.
Steps to reproduce

Install two Instagram instances in separate LiveContainer containers
Enable "Isolate App Group" for both containers
Enable "Spoof IDFV"
Log into an account in container #1
Open container #2 — Instagram login screen shows "Continue as [account from container #1]"

Expected behavior
Each container should have fully isolated keychain. Instagram in container #2 should not see any accounts from container #1.
Actual behavior
Instagram in container #2 suggests the account from container #1 via "Continue as" prompt. keychain-access-groups correct: NO in JITLess Diagnose.
Environment

LiveContainer version: 3.6.65
Installed via: SideStore
Device: iPhone 16 Pro Max (iOS 26.2.1)

Originally created by @olejenek500-web on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/1154 Description When running two Instagram containers with "Isolate App Group" enabled, the second container still shows "Continue as [account]" on the login screen — suggesting the account logged in from the first container. In Settings → JITL-Less Mode Diagnose → Entitlement File, keychain-access-groups shows Correct: NO, which means keychain isolation is not working between containers. Steps to reproduce Install two Instagram instances in separate LiveContainer containers Enable "Isolate App Group" for both containers Enable "Spoof IDFV" Log into an account in container #1 Open container #2 — Instagram login screen shows "Continue as [account from container #1]" Expected behavior Each container should have fully isolated keychain. Instagram in container #2 should not see any accounts from container #1. Actual behavior Instagram in container #2 suggests the account from container #1 via "Continue as" prompt. keychain-access-groups correct: NO in JITLess Diagnose. Environment LiveContainer version: 3.6.65 Installed via: SideStore Device: iPhone 16 Pro Max (iOS 26.2.1)

kerem closed this issue

2026-03-03 15:37:59 +03:00

kerem commented

2026-03-03 15:38:00 +03:00

Author

Owner

@hugeBlack commented on GitHub (Feb 17, 2026):

That's probably because you installed LC+SS through iloader. You can reinstall lc in built-in sidestore to correct that or reinstall in Impactor

@hugeBlack commented on GitHub (Feb 17, 2026): That's probably because you installed LC+SS through iloader. You can reinstall lc in built-in sidestore to correct that or reinstall in Impactor

kerem commented

2026-03-03 15:38:00 +03:00

Author

Owner

@olejenek500-web commented on GitHub (Feb 17, 2026):

That's probably because you installed LC+SS through iloader. You can reinstall lc in built-in sidestore to correct that or reinstall in Impactor

Thank u!

@olejenek500-web commented on GitHub (Feb 17, 2026): > That's probably because you installed LC+SS through iloader. You can reinstall lc in built-in sidestore to correct that or reinstall in Impactor Thank u!