I set up the Facebook login correctly (I'm able to log in using the Facebook button and retrieve the profile data). I followed The FB Developer guide to set up the SSK and the LoginButton.
The issue arise when I go back the button and I want to log off. This is what I get:
-[UILabel loginButtonDidLogout:]: unrecognized selector sent to instance xxxxxxx
***Terminationg App due to uncaught exception 'NSInvalidArgumentException', reason: '-[UILabel
loginButtonDidLogout:]: unrecognized selector sent to instance xxxxxx'
The class Is loaded in the appDelegate file with
[FBSDKLoginButton class];
in the .plist application file the -ObjC switch is set in the linker section.
Any ideas?? Thanks in advance
Found the issue! I was migrating from Facebook SDK v3.4 to v4. As I had a view already done for the previous login Button, I just recycled it and changed the class as the tutorial says. Deleting the view from the Storyboard, adding a new view and changing class to FBSDKLoginButton made everything work smoothly.
Thanks anyway rmaddy!
Related
For some reason whenever I add a text field to my project and try type in it, the app crashes.
The errors I get are:
Can't find keyplane that supports type 4 for keyboard iPhone-PortraitChoco-NumberPad; using 1336863583_PortraitChoco_iPhone-Simple-Pad_Default
-[NSNull length]: unrecognized selector sent to instance 0x1018b1d80
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull length]: unrecognized selector sent to instance 0x1018b1d80'
This happens in both the simulator and on device. I have unchecked "Connect Hardware Keyboard" in the simulator settings also.
Do I have to handle each and every input?
So I saw a solution deep in a forum, and it did actually solve the issue.
For some reason the tab bar controller I was using was causing the issue. Simply deleting the controller, and then going Editor > Embed In > Tab Bar Controller and re adding the views fixed it.
I'm trying to integrate a Facebook login with my Parse backend. Upon running the app, I receive
[PFFacebookUtils initializeFacebookWithApplicationLaunchOptions:]: unrecognized selector sent to class xxxxxx
on the line
PFFacebookUtils.initializeFacebookWithApplicationLaunchOptions(nil)
or
PFFacebookUtils.initializeFacebookWithApplicationLaunchOptions(launchOptions)
I have tried the solution here: https://developers.facebook.com/docs/ios/troubleshooting#unrecognizedselector
(adding the -ObjC flag), and have cleared Derived Data, to no avail.
I'm using Parse SDK 1.7.2, Facebook SDK 4.0.1, and the PFFacebookUtilesV4 framework.
The full error is as follows:
2015-05-03 14:22:25.742 hotPotato[49116:1453068] +[PFFacebookUtils
initializeFacebookWithApplicationLaunchOptions:]: unrecognized
selector sent to class 0x10f524048 2015-05-03 14:22:25.810
hotPotato[49116:1453068] *** Terminating app due to uncaught exception
'NSInvalidArgumentException', reason: '+[PFFacebookUtils
initializeFacebookWithApplicationLaunchOptions:]: unrecognized
selector sent to class 0x10f524048'
I faced same issue.
My mistake was that I also added ParseFacebookUtils.framework in the project.
Just remove it and everything will be fine :)
Make sure that you have imported the correct frameworks into your bridging header:
#import <FBSDKCoreKit/FBSDKCoreKit.h>
#import <ParseFacebookUtilsV4/PFFacebookUtils.h>
Also check that the needed frameworks are included in the Linked Frameworks and Libraries list under your target's General tab.
If you've added the frameworks manually, go to the Build Settings tab, and make sure that Search Paths contains the paths to the Parse and Facebook frameworks.
Mine looks something like this:
$(inherited)
$(PROJECT_DIR)/Vendor/Facebook
$(PROJECT_DIR)/Vendor/Parse
The PFFacebookUtils initialization call in the application(application:, didFinishLaunchingWithOptions:) delegate method should follow the Parse initialization method:
Parse.setApplicationId("<APP_ID>", clientKey:"<CLIENT_KEY>")
PFFacebookUtils.initializeFacebookWithLaunchOptions(launchOptions)
If you haven't done this already, I suggest that you consult Parse's own guide:
https://parse.com/docs/ios_guide#fbusers-setup/iOS
My problem was solved by making all my frameworks including my Parse ones referenced instead of copied.
Probably a little late but I solved this by using the Bolts.framework from the Facebook SDK as opposed to the Parse SDK.
Edit: This is not a duplicate of any other question on SO - which I already researched. I understand what an "unrecognized selector sent to class" error message means and how to troubleshoot them. This error is unique to Amazon Web Services SDK for iOS and its frameworks, nothing that I wrote or could troubleshoot as suggested by #Hot Licks.
I have been working on this issue for some time. In the process of debugging and authentication starting to work, Cognito Sync began to fail.
My code:
AWSCognito *syncClient = [AWSCognito defaultCognito];
fails with the error:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[AWSEndpoint endpointWithRegion:service:]: unrecognized selector sent to class
The headers used:
#import <AWSiOSSDKv2/AWSCore.h>
#import <AWSCognitoSync/Cognito.h>
I am using SDK 2.0.17.
This code worked while users were unauthenticated. Once authentication started working, I get this error. I also upgraded from SDK 2.0.8 to 2.0.17 during the authentication debug process. Any ideas out there?
It seems like you have upgraded AWSiOSSDKv2.framework to 2.0.17, but AWSCognitoSync.framework is still 2.0.8. Please make sure to use the same version for both frameworks.
I have implemented the AdWhirl to show different network Ads but while it shows the ads on my view and I tap to open the ad it crashes with the following displayed in the log
-[AdWhirlAdapterIAd helperNotifyDelegateOfFullScreenModal]: unrecognized selector sent to instance 0x9fce850 2012-12-08
19:40:27.571 ExerMemosApp[2294:1b203] * Terminating app due to
uncaught exception 'NSInvalidArgumentException', reason:
'-[AdWhirlAdapterIAd helperNotifyDelegateOfFullScreenModal]:
unrecognized selector sent to instance 0x9fce850'
I searched too much but couldn't find solution. Give me suggestion to remove this error.
Thanks in advance
Are you sure that the AdWhirlAdNetworkAdapter+Helpers.h file is included in your project? Make sure everything under AdWhirl/Internal is correctly referenced in your build settings.
you are not having helperNotifyDelegateOfFullScreenModal method in your File. Check that one because the name says, its delegate method. you might forgot to implement that method
I'm getting a strange exception in Xcode 4.2.1 (ARC-enabled project) that I can't track down to the root of the problem.
This is what the exception looks like:
2012-03-18 22:19:32.855 Project[14225:707] +[UIPickerTableViewTitledCell isEqualToString:]: unrecognized selector sent to class 0x3f2bbec4
2012-03-18 22:19:32.859 Project[14225:707] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[UIPickerTableViewTitledCell isEqualToString:]: unrecognized selector sent to class 0x3f2bbec4'
What is a UIPickerTableViewTitledCell? I suppose it is some internal class for the UIPickerView to use. But I'm not referencing that class anywhere in my project.
My application is setup as a Tab Bar application with a navigation controller in each tab and this particular tab has a tableview and pickerview.
It sounds like you have an over-released object. I get that when in pre-ARC code, release is called one too many times. The code sounds like it is looking for an NSString to send isEqualToString: to but instead of getting the NSString which has been released already, it gets this random instance of UIPickerTableViewTitledCell.
I would enable Zombies. In Xcode 4.2.1, you can find it in the menu item Product > Edit Scheme. Go to the Diagnostics tab. Then there is an Enable Zombie Objects checkbox. This will make your over-released object into a Zombie, so you can figure out exactly what object is causing your crash.
I would read the Apple doc Technical Note TN2239: iOS Debugging Magic for more in-depth information on this. The whole doc is great, but you can start off by reading the sections titled "Zombies!" and "More Zombies!"