-
-
Notifications
You must be signed in to change notification settings - Fork 875
Getting weird crashes PFObjectSubclassingController.m #980
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
Same here. My app was sent to a beta review a few hours ago: http://crashes.to/s/dc1ff26327c I'm rocking iOS SDK v1.14.1. |
Same here. Crash when starting the app in the Simulator. PFObjectSubclassingController.m: char potentialPaths[2][PATH_MAX] = { };
strncpy(potentialPaths[0], bundle.executablePath.UTF8String, PATH_MAX); // crash
realpath(potentialPaths[0], potentialPaths[1]);
The offending bundle is
|
Why not just use the |
I submitted recently an the app to review with 1.14.1, and I got 361 crashes in one device 😨 (apparently they are running the app in some devices before it enters in review): |
We've fixed the issue for us in https://github.com/Widgetlabs/Parse-SDK-iOS-OSX/commit/aaa0632235b0896f5738a234e89a4a377d7eb68c. You can use it in your # https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/980
pod 'Parse', :git => 'https://github.com/Widgetlabs/Parse-SDK-iOS-OSX.git', :branch => 'patch-1' But I'd recommend to either fork our fix or else use Parse SDK |
Thank you! @fluidsonic |
@fluidsonic This worked for me. My code was crashing anytime I initialized an object in the AVFoundation framework, e.g. |
This will scan all loaded code bundles for classes which inherit from `PFObject`, and register them upon Parse initialization. Still have opt-in support for manual-only registration, though it shouldn't be necessary for most cases.
This is getting merged in a few moments and release is coming soon. |
@nlutsenko thats what I was talking about in #975 |
1644 crashes with only 5 users
PFObjectSubclassingController.m line 355
http://crashes.to/s/d1678763779
anyone know how to solve this?
The text was updated successfully, but these errors were encountered: