iphone application crashing

What Yahoo! service are you integrating? Are you using the Objective C SDK? Can you please provide technical information about the problem?

- Jon

Are you able to compile and run the sample app with your own api and secret key? Do it crash when you start the app?

I'm using the sample code as it is, and added the consumer key, secret and app ID. That's all the changes I made. Start the app and it crashes

hi there again,

i downloaded the code,
obtained the API KEY, shared secret and Application ID.

Now i have open the social app project

set the key,secret and app id

self.session = [YOSSession sessionWithConsumerKey:@"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
andConsumerSecret:@"XXXXXXXXXXXXXXXXXXXXXXXX"
andApplicationId:@"XXXXXXX"];

now when ever i run the application, its get crashed and the reason is

obj_msgSend

Please do let me know , why its happening like this,

Yahoo application gets crashed , i never expected .

Now application is not at all crashing.

When ever i run the application , its getting closed and safari is getting opened up,
where its asking for user id and password , after logging in i am getting a TOKEN .

I assume that session is created now ,
but when ever again i restart the application same process is getting carried out , its getting closed and asking for user id and password.

Please let me know how to move forward !
My aim is to only set the chat status of the user.
Will be thankful for the help
warm regards
sindhu tiwari

You can try to use a custom URL scheme to launch your app. Then set that URL as the callback URL.
Once you are able to authenticate from Safari, click continue and it should launch your app and sends back the necessary authentication parameters.
I have gotten this to work a month back. The last time I checked was yesterday and it did not work anymore. I'm not sure if it is a problem with the Safari in SImulator in the new SDK, or something changed at Yahoo.

A work around for me, I modified the code to not launch Safari, but instead do the authentication in a webview within the app. After authentication, click continue. I use – webView:shouldStartLoadWithRequest:navigationType:
to check for the callback URL that I specified. If it matches, I closes the webview, and passes the parameters to the app for authentication. This works fine.

Encountered problem with sendUpdate instead