It’s not intentional for the app to crash when asking for extra permissions – at most the native layer should throw an async JS error that you can handle, and perhaps it shouldn’t err at all but we’ll need to look more at the FB SDK documentation. I’ve created an internal issue to track this.
Is there anyway to request this permission? I’ve read that this error happens elsewhere (in other sdk’s) because you are specifying the “manage_pages” permssion as a readPermission, not a writePermission. That might be whats happening here.
I would recommend looking into uri Linking: https://stackoverflow.com/a/5707825 Basically you can send someone to the facebook app with a post queued up. FBSDK is a scary framework and Facebook / iOS relations have been shifting a lot in iOS 11. Sending a user directly to the app with your content ready would be the most stable move regardless of Expo
Hello expo team, thank you for your response on this issue. We’re an x-googler startup using Expo and are currently blocked by this issue. manage_pages is not just a write permission, it’s also the primary permission needed to access the new Instagram Graph API. Without this permission the APi is completely locked out.
See https://developers.facebook.com/docs/instagram-api/getting-started “You’ll need manage_pages to get your Page’s ID, which you can then use to get your Instagram Business Account ID.”
It’s unfortunate that facebook made decision to overload this permission for both, getting IDs and writes, but that is the reality we’re in.
Can you suggest any workarounds for ti? Facebook appears to be sunsetting the original instagram API so this will effect more users in the near future.
See full deprecation schedule here:
We will be deprecating the older Instagram API Platform in three phases with complete deprecation occurring in early 2020. The following will be available until July 31, 2018:
Follower List - to read the list of followers and followed-by users Relationships - to follow and unfollow accounts on a user’s behalf Commenting on Public Content - to post and delete comments on a user’s behalf on public media