Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

forceful resizing of non true ipad apps #311

Open
AnkitFGM opened this issue Jan 15, 2025 · 4 comments
Open

forceful resizing of non true ipad apps #311

AnkitFGM opened this issue Jan 15, 2025 · 4 comments

Comments

@AnkitFGM
Copy link

AnkitFGM commented Jan 15, 2025

Describe the issue

Instagram which is a mobile sized app when installed on ipad through live container results in forceful resize of insta.
for better understanding, i am uploading an screenshot

Device : iPad pro 2020
Installed through : Sidestore 0.5.10

Jit Less

IMG_5314

Instructions to reproduce

Just normally install any non true ipad app like instagram,whatsapp on ipad

What version of LiveContainer are you using?

3.2.0

Other

No response

@AnkitFGM
Copy link
Author

AnkitFGM commented Jan 17, 2025

found a workaround. Instead of installing 2nd container from primary container. I Downloaded a fresh live container ipa file.
Unzipped it.
removed ‘2’ from uidevicefamily.
Changed cfbundledisplayname to ‘livecontainer2’.
Changed cfbundleidentifier to com.kdt.livecontainer2
Changed cfbundlename no livecontainer2
changed CFBundleURLName to com.kdt.livecontainer2.urlscheme
changed cfbundleurlschemes to livecontainer 2.
Then sideloaded it using 2nd slot of sidestore.
Change Affected apps to shared folder.
Open those apps in 2nd container.
Everything seems to be working in sync.

Image

@hugeBlack
Copy link
Collaborator

Yes, this can be a workaround but one of the 2 live containers has to be in iPhone mode all the time.

Unfortunately, iOS decides whether the app can run in iPad mode by reading Info.plist, which happens before live container starts, so I think it's unlikely to solve this issue apart from this workaround.

@AnkitFGM
Copy link
Author

Local notifications doesn’t work in 2nd container installed through this workaround.
Anything i shouldn’t have changed in info.plist which might be causing this?

@hugeBlack
Copy link
Collaborator

Well, that's a bug, I'll fix that soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants