-
Notifications
You must be signed in to change notification settings - Fork 19
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
how do i add a load command? #42
Comments
Good questions, and I don't have a good answer at the moment. The code currently cannot add or remove load commands, it just has limited support for changing existing load commands as long as those changes don't change the size of those commands. I have a use case for other changes to the load commands (in particular removing some load commands and moving around other load commands to redistribute "free" space to be able to grow some payloads), but that will require some research on my side. |
What I don't understand is why you're trying to use macholib for making these changes. Your question seems to indicate that there's something wrong with the build of an app bundle and IMHO that should be fixed at the source instead of trying to fix it during the upload to Apple. |
It's pretty straightforward and you're close. You're missing:
|
i have no idea what i'm doing, so forgive me if i'm doing something (or everything) wrong.
context
even though i don't have a mac and know nothing about iOS development, i'm trying to fix a framework for a
.ipa
file that seems to have been compiled wrong. i get this error when trying to upload it to testflight:i used
lipo
as mentioned here to remove unused architectures but it didn't work. as far as i can tell that wasn't the only issue because i don't see the ITMS-90087 and ITMS-90209 errorsrunning out of options i decided to try and see if i can just add the load command to the binary manually. using both
otool
and this library i was able to verify that this framework does not contain theLC_ENCRYPTION_INFO
command.code
error
i don't get any errors when writing to the file but attempting to read the binary again after making that change cause the following error:
The text was updated successfully, but these errors were encountered: