You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to reply a tweet with “– (NSString *)sendUpdate:(NSString *)status inReplyTo:(unsigned long)updateID” method, "in_reply_to_status_id" field in the response string is empty.
At first, I had to change the type of updateID from “unsigned long” to “unsigned long long”, otherwise some part of the updateID parameter was truncating(because of the 32 bit issue I guess, as I’m trying on IOS).
After that everything seemed working, I was using the method above for replying a tweet and my reply tweet is sent to twitter perfectly but the problem is my reply tweet does not appear to be a “reply tweet”; it just appears as a usual tweet.
When I check the response of my reply tweet above everything seems OK except that “in_reply_to_status_id” field seems empty which explains the situation(my reply tweet seems like a usual tweet) I tried to explain above.
The text was updated successfully, but these errors were encountered:
While trying to reply a tweet with “– (NSString *)sendUpdate:(NSString *)status inReplyTo:(unsigned long)updateID” method, "in_reply_to_status_id" field in the response string is empty.
At first, I had to change the type of updateID from “unsigned long” to “unsigned long long”, otherwise some part of the updateID parameter was truncating(because of the 32 bit issue I guess, as I’m trying on IOS).
After that everything seemed working, I was using the method above for replying a tweet and my reply tweet is sent to twitter perfectly but the problem is my reply tweet does not appear to be a “reply tweet”; it just appears as a usual tweet.
When I check the response of my reply tweet above everything seems OK except that “in_reply_to_status_id” field seems empty which explains the situation(my reply tweet seems like a usual tweet) I tried to explain above.
The text was updated successfully, but these errors were encountered: