We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I had bought a new macbook.
With compiling the newly pushed code with #316 fixes , doesnt commit the ipatool to keychain, it doesnt even can create the entry.
What i did, was to compile the code with go lang (git clone.. etc) and firstly run the release binary 2.1.4
With this tool, i managed to get the error (the known one name="" ) and error on download ipa.
Go to key-chain add the Store-front-id as always from previous issue, and then run the newly compiled tool, but DO NOT revoke.
just re login: with only -e
ipatool auth login -e ... This time will fix the name="Your actuall name" and the download will start immediately.
So the compiled latest code doesn't work standalone without the old binary in never used machines before.
2.1.4
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
I had bought a new macbook.
With compiling the newly pushed code with #316 fixes , doesnt commit the ipatool to keychain, it doesnt even can create the entry.
What i did, was to compile the code with go lang (git clone.. etc)
and firstly run the release binary 2.1.4
With this tool, i managed to get the error (the known one name="" ) and error on download ipa.
Go to key-chain add the Store-front-id as always from previous issue,
and then run the newly compiled tool, but DO NOT revoke.
just re login: with only -e
ipatool auth login -e ...
This time will fix the name="Your actuall name"
and the download will start immediately.
So the compiled latest code doesn't work standalone without the old binary in never used machines before.
Version
2.1.4
Relevant log output
No response
The text was updated successfully, but these errors were encountered: