NSPlaceholdeeString initWithString in Facebook SDK crashes app - objective-c

I have an app that contains some basic Facebook integration such as logging in and pulling one's albums (and consequently, photos) from Facebook for some later image processing.
However, some time during the past few days, I started getting crashes for [NSPlaceholderString initWithString] nil argument for some reason. The crash only happens when the user wants to connect to Facebook and nowhere else (I also allow image retrieval from Bing, Camera and Photos app).
Does anyone know why it's happening? It's weird to have it happen out of nowhere...I've not touched the Facebook code in months and it used to work properly.
I would post some code, but I don't know where it's all coming from...

Related

Using admob again in the application that received the warning "Ad serving is limited"

I started getting a warning saying "Ad serving is limited" in my React Native app and ads are no longer showing. I also use my app on PlayStore and naturally I can see my own ads. When I researched, I found out that this is prohibited and I never thought it would be illegal. I don't want to work with any other ad service other than Admob. I have two questions regarding this situation:
1- Is it okay if I open a new admob account and put ads in the same application again and add my own device as a test device this time? I mean, don't I have the right to do something like this because this practice was penalized before?
2- Where can I find a list of such strict rules in order not to experience a similar situation?
Not problem if you only opening the app to see the ads, but it's forbidden to click the ads.
It's not allowed to have 2 admob account per user, once it found out, your both admob can be banned permanently.
https://support.google.com/admob/answer/9686306?hl=en
Check again how you serve your ads, I have limited ads before, then I found what the reason and update the apps, limit got removed within one week.

iTunes Connect doesn't ask for updated screenshots?

I've updated my iPhone app to support the iPhone 5 screen..
I've done this before for another app and I was forced to upload new screenshots taken with the iPhone 5.
This time however, iTunes Connect just displays the status as "waiting for review" and isn't mentioning anything about the screenshots..
I'm slightly worried something has gone wrong? App works great on iPhone 5 and simulator though.
It turns out Apple can block apps during the review process that have something wrong with metadata. If they decide your metadata is wrong they'll just change your app's status to "Metadata Rejected".
Here's the quote from the rules for this status:
Appears when specific metadata items aside from your binary have not
passed review. To resolve the issue, edit the metadata in iTunes
Connect and your existing binary is then reused for the review
process. You receive a communication from App Review in the Resolution
Center regarding the reason for the metadata rejection.
When things change to the AppStore (Apple adds a device) they might require you to get new screenshots. But if nothing changed in their system, it's normal that they don't ask.
Don't worry!
They copy over the screenshots from your last version of the app (or is your Retina4 screenshot section in itunesconnect empty?). So if you donĀ“t want to update them, it should be okay like this.
Chances are your app has not hit review (and now as of the 21st) and won't be reviewed until after the 29th. Once your app hits review, it will become rejected for the missing screenshots. If you want to save yourself some time and pain, update the screenshots while Apple is on their downtime for the Christmas holiday. You'll thank yourself later.
My app got accepted yesterday, no word about the screenshots.
App works fine on iPhone 5, mailed Apple to complain this probably is a bug (iTUnes Connect does not recognize localized Default.png, which is what is checked to verify it is iPhone 5 optimized I believe.)

me/photos and albums not returning all photos

When I make a request to me/photos I should expect to get all photos that I've been tagged in. However, I am not getting this behavior. There seems to be a few pictures here and there that are missing from the JSON results. When I go on FB, they are visible to me.
This is happening to some albums as well.
Any thoughts?
Facebook's App Settings page allows users to change the exposure of their content to applications other people use.
Screenshot: http://i.stack.imgur.com/vve6b.png
If I have prevented applications from viewing my photos, when you login to a Facebook application you will not be able to see any photos I have uploaded. This is still the case even if I have tagged you in my photos.
If you, however, visit the Facebook website directly you will be able to see all the photos you have been tagged in.
This accounts for the discrepancy we have been seeing.
Tested using 2 Facebook accounts.

iPhone up to date Twitter oAuth tutorial

Could someone please give me a single up to date tutorial for implementing OAuth with twitter. I have gone through so many tutorials I have lost count, and not a single one of them is up to date with the new xCode. I tried the MGTTwitter, but there is no tutorial for it. On his own website, where it gives link to tutorial, it just links you to this
http://ww35.2bros1blog.com/2010/07/switching-from-basic-to-xauth-with-mgtwitterengine-on-iphone/
So no idea that that is about
I tried
http://www.icodeblog.com/2010/09/16/dealing-with-the-twitter-oauth-apocalypse/
But I dont know how to add the static folders to xCode. I tried adding the targets, but nothing to add.
Tried following
http://mobile.tutsplus.com/tutorials/iphone/twitter-api-iphone/
However, it is out of date. When I run the app, using my consumer key and secret, when I click authorise, it just closes window, then brings up authorisation window again. I enter user and pass again, does the same thing over and over again.
I downloaded latest version of sharekit, didnt really want to go down this root as all I want is the twitter authorisation and I think adding over 50 files or so is a bit much for one feature, but thought I would give it a shot. But when I open it up, comes up with error around facebook
(null): error: /Users/adam/Downloads/ShareKit-ShareKit-7a05403/Classes/ShareKit/Sharers/Services/Facebook/../../../../../Submodules/facebook-ios-sdk/src/FBDialog.bundle: No such file or directory
All I want is a simple authentication so users can accept and then send tweets from the app. I dont want to use the twitter framework as then users have click send twice, i.e type message into textview, then then twitter viewcontroller appears, then they click send again. I want them to be able to tweet from within the app. Yet I just cannot seem to find any tutorial that explains how to do this in detail.
Could someone please point me in the direction of a tutorial that does this, I didnt think it would be this much hassle to implement a simple authorisation into iPhone, but this is driving me insane!!!
Edit:
I got
http://www.icodeblog.com/2010/09/16/dealing-with-the-twitter-oauth-apocalypse/
This one working, however when I sign in, app crashes and the log says
Authenticated with user (null)
Anyone have any idea about that one?
Found out why I was having a problem with these twitter tools. They were using http rather than https to authenticate with Twitter which is no longer allowed. Just changed it to https and works fine

Re-activating a Facebook App

I want to know if it is possible to re-activate a Facebook App that has been previously disabled.
This is what happened:
We created a Facebook App and an iPhone App that connect to each other. After releasing our game to App Store, one of our programmers accidentally deleted the App from Facebook. Now players are shown a message saying the Facebook App does not exist.
We know this may not be possible, but still wanted to ask.
I work on the platform team at Facebook.
Unfortunately there isn't a standard way to do this since this isn't a situation that occurs often. However, I can imagine how painful this may be. If you could provide me with either of the following - the app namespace, canvas/connect URL for the app or the app ID, we may be able to help.