-
Notifications
You must be signed in to change notification settings - Fork 7
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
Runs fine for the first time #2
Comments
Stange problem. Can you delete the injection project and try again without changing the codesigning. It should be fine ad-hoc. I can TeamView if you want me to take a look. |
Let me try that and come back to you. Really, teamviewer? You're awesome! |
Guess that didn't work :( |
How do I do that? |
If you send your TeamViewer co-ord to injectionapp at johnholdsworth.com I can take a look |
I'm experiencing the same issue (first injection works, subsequent fail with a However, I'm not sure that this is a complete solution, as I am not able to get injection fully working as I subsequently experience an issue which I've detailed in #10 after the swizzling stage. |
That was it yes @sibljon, I'll try to do what you've done. But do you do it all the time that you inject? |
Yes, unfortunately I have to manually delete the directory every time I
inject :-/
El El vie, ene. 13, 2017 a las 3:41 PM, Marcel Schmitz <
notifications@github.com> escribió:
… That was it yes @sibljon <https://github.com/sibljon>, I'll try to do
what you've done. But do you do it all the time that you inject?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAa_wwR9sxtG1yuUuuNAXZs8qRZM0y-oks5rR40ngaJpZM4LeUMc>
.
|
The first time I run this (InjectedCount = 1), all runs well, all other consequent attempts fail with the sign code issue.
I've code sign the bundle project, hence working for the first time. Don't know how to sign the consequent bundles.
Any thoughts?
The text was updated successfully, but these errors were encountered: