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

Plistbuddy and merge of plist files #55

Open
strano666 opened this issue Nov 14, 2018 · 0 comments
Open

Plistbuddy and merge of plist files #55

strano666 opened this issue Nov 14, 2018 · 0 comments

Comments

@strano666
Copy link

strano666 commented Nov 14, 2018

I'm trying to use the functionality to merge two Info.plist, but i've an error during the making of the package.

> Making all for tweak alfonso…
make[2]: Nothing to be done for `internal-library-compile'.
> Making stage for tweak alfonso…
==> Unpacking sg.vp.UnCrackable-2.ipa…
==> Copying resources…
==> Setting bundle ID…
==> Setting display name…
==> Merging Info.plist…
==> Copying dependencies…
==> Injecting dependencies…
==> Error: Failed to inject alfonso.dylib into UnCrackable Level 2.app
make: *** [internal-package] Error 1

I think that the problem is the plist merged, because it result to be the plist into Resources dir.

Inspecting the code of ipa.sh, i've added at line 36 the redirect of the stderr: the message catched is
Merge: "Level" Entry Does Not Exist
Plus i've recovered the $STAGING_DIR/Info.plist (that is equal to the plist in the Resources dir) and $info_plist

The error captured does not tell me anything, but maybe there is some problem about "parsing" into sh script, because the word "Level" i can find only into the first plist generated from theos-jailed. It is part of the name of the app.
The plist to merge is here.
Sorry if the last consideration is a blasphemy :)

EDIT: if i add the backslash for the command at line 36, the error of Plistbuddy disappear, but there is still the same problem.
/usr/libexec/PlistBuddy -c "\"Merge $info_plist\"" "$STAGING_DIR/Info.plist"

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

No branches or pull requests

1 participant