-
-
Notifications
You must be signed in to change notification settings - Fork 878
SDK breaks signature in Swift project #92
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
Comments
Hey @alexbat98, Tested right now running ParseCrashReporting both on the simulator and building and running on the device - everything works like a charm, so I suspect there is something about your project configuration specifically that blocks it. Can you share a more concrete example or a repro project? This would help us in identifying the root cause and fixing it for you in a fast manner. |
@nlutsenko I can't share my sources here. So, I emailed you with an address provided in your GitHub account. Thanks for help. |
Just got it, thanks. I'll take a look in depth tomorrow and post here. |
Managed on my own. I deleted my project and cloned it from git repo to another directory (reverting changes doesn't work). Then I followed instructions on parse.com. For some reason, first time I did it Parse and Bolts appeared in the Embedded binaries sections. That breaks the project. Now they are in the Linked Binaries section. Everything works like a charm. |
I added Parse SDK to my existing iOS project. Everything was OK. Then I added ParseCrashReporting. Now I can't start my app on a real device. Xcode fails with the following message: "App Installation Failed, The application does not have a valid signature". Tried cleaning project and recreating provisioning profile. Nothing helps.
The text was updated successfully, but these errors were encountered: