This is now the 4th time I am sending my app for review. I want to use Instagram Basic Display API and therefore require instagram_graph_user_media permission to access media (and incidentally instagram_graph_user_profile). I have 2 test users, my personal IG account with a bunch of pics and a test user that I created with an empty feed. I can login with both users. But when the Instagram app reviewer is logging in, my app can't access their media. I successfully retrieve the access token but when comes the time to call the Graph API here is what happens:
https://graph.instagram.com/me/media?fields=media_type,media_url,permalink,thumbnail_url&access_token=IGQV....
returns
{"error":{"message":"Application does not have permission for this action","type":"IGApiException","code":10,"fbtrace_id":"A99vuaAC41DSvlt0Hxvcly-"}}
Here is an update from my latest app review rejection. This time, I added the code above to catch code 10 errors and if I did, try to fetch the user profile data. Guess what, that failed with a code 10 error as well. So, whatever the app reviewer is doing, it is granting access to neither the profile or the media API.
Another update. The reviewer I had this time sent me two screenshots, one of the Instagram login screen and one of my app's error screen. Interestingly, the Instagram login screen had a strange Instagram username that I have never heard of before. It certainly wasn't my test Instagram account. So I now have evidence of them both using my test account and their own special test accounts.
The question in my mind now is, is there something special about their test accounts that ruins the process? After all, I have not added them to be testers of my app, although if someone who hasn't accepted my test invite tries to log in, it errors in an entirely different way.
I am running out of ideas here. My next thing to try is to exchange the short-lived access token for a long-lived token, as well as trying to use the new access token to server-side (where I exchange the code for the access token) to check if the access token ever works or if it is created with insufficient access.
This whole process is a nightmare.
I will put this as an answer because we have dealt with this thing now for over 2 weeks and quite a few submissions. I think you should remove the bounty though.
What you have done so far:
Created and approved IG test accounts
Double and triple checked parameters & permission
Tested your app a dozen times
Created dozens of screencast spoon-feeding, making sure a 5 yo kid would be able to test your app
Having the above, I am sure you noticed:
The reviewer will add a generic text as 'reject reason.'
The reviewer will submit the irrelevant and out-of-scope screenshot(s)
The reviewer will not test with the Instagram credentials provided.
Maybe he WILL test with the Instagram test credentials provided (in fact you're left in the dark as to how they actually simulate IG access)
The reviewer will claim he's unable to sign in using provided credentials
The reviewer claims having tested, but you see no traces in your DB whatsoever (would be smart to do so, to know whether they're actually doing something or not, up to a certain point)
Conclusion
You have to know that your app is at the reviewer's mercy and approval sometimes arbitrarily. Eventually, you will find your app being approved while having submitted it to change at all.
This should be obvious but when you are so deep in the hole and try to think why your app is being rejected you stop thinking logically.
Here is what I did:
Create a dummy Instagram account.
Link this account to an email provider that doesn't require a phone/another way of verification (I used ProtonMail).
Use an Instagram Tester account (do the whole process).
In your instructions let the reviewer that they need to log in to ProtonMail to get the Instagram confirmation code; since they will do login from an unknown location (if you could simulate the above in your screencast that would be great, but I didn't do it).
If you apply for both instagram_graph_user_profile and instagram_graph_user_media you need to do this in 2 steps individually.
The second step getting the instagram_graph_user_media permission is much easier.
I lost a couple of days and tried everything and anything before I realized that.
Hopefully, this should help someone that is having the same problem.
The app was approved the first time.
It is possible that the App Reviewer is unchecking the instagram_graph_user_media access in the authentication screen, thus giving you only access to instagram_graph_user_profile. I had the exact same error code being thrown back my way, and I did the following:
Catch the error code 10 error
Try to fetch the https://graph.instagram.com/me?fields=account_type,username&access_token=${accessToken}
If that works, then display a page that makes it clear that you have successfully connected to the Instagram User Profile (and here is your username and account type) but, if the user wants to do X they also need to approve media access, and here is a button to go and reauthenticate again.
See the image I have below.
Now, I did the above and I still got an app review failure of code 10, which means that the second fetch to only the username and account type failed, and I do not know how they could possibly have managed to do that.
They admitted issue but not fixed yet: https://developers.facebook.com/support/bugs/543633182940083/
To get approved for Instagram Basic Display:
create a Facebook test user
create an Instagram account with that FB test user
give the credentials (email/address) of the Facebook test user to the reviewer in the Instagram Basic Display submission
Basic Display API review process is so bad its beyond words. I have been hitting the brick wall of their rejections for 3 weeks and almost got bald by pulling my hair in frustration. You really have to read between the lines to get a hint of what they are doing.
Turns out what the reviewer was doing is selecting "Continue with Facebook" on the Instagram Login screen and going that route (via Facebook login) instead of entering the instagram credentials directly. Only once I realized that I was able to pin point the problem. Interestingly though testing on the Simulator was fine but the problem only became apparent once I tested on the real device. The reason - simulator doesn't have neither Facebook app nor Instagram app installed, so it behaves differently versus the device where these apps get involved in the flow via deep linking.
The bottom line:
Test on real device.
Make sure to test both the direct Instagram log in and the "Continue with Facebook" option.
Test on the device with and without the Facebook and/or Instagram app installed.
Make sure to use brand new instance of WKWebView with non persistent data store to bring up the login screen, so that it doesn't have any cookies from previous logins:
let configuration = WKWebViewConfiguration()
configuration.websiteDataStore = WKWebsiteDataStore.nonPersistent()
let webView = WKWebView(frame: .zero, configuration: configuration)
Pray the God of your choosing.
I had an app that was working fine with inapp purchase - I still was in test mode but it was fine.
Then I decided to go to production but got issues - in the meantime nI had lost my certificate keys, so I had to use another package name, upload a new app on Google play and use new certificate credentials.
Anyway.
I did the exact same thing with this new app, and I also add the inapp purchase package, but when I launch the app I have this error :
Error while retrieving the informations from the server ([DF-AA-20])
Any idea of why I have this error message ?
I checked the inapp package name several times and it's ok...
What could be the issue ?
I've been trying to solve this for hours...
Thanks for your help.
I was able to solve the issue by doing these steps:
- I copied the public key found in "Services & API" google account and added it in my code
- I published the app in alpha mode and had to wait until it was really "published", and not "pending publishing"
Now it's working fine and I'm able to make test purchases.
But then I deleted the test account and tried to make a real purchase, and I'm having this error:
"Error: Impossible to buy this article"
Does anybody had this issue ?
Thanks
for a my UWP App I have created an extension for Edge and Chrome.
I have tried to create a new submission to the store but I have received the following errors:
com.microsoft.edge.extension is a reserved extension type. Your app does not have permission to use this extension type. To request permission, please use our extension submission form: https://aka.ms/extension-request
Your developer account doesn’t have permission to submit apps converted with the Desktop Bridge at this time. https://aka.ms/desktopbridgeforwindowsstore
I have fill the module at https://aka.ms/extension-request and at https://aka.ms/desktopbridgeforwindowsstore but, after 1 month, I didn't received any response.
Somebody know what I have to do in order to continue with the submission?
Does somebody have any experiences on that?
P.S.: I have sent a post at the MSDN forum and I have asked support at the Microsoft Answers but anybody was able to help me on that.
Thank you,
Regards,
MatVic
It's working in test mode, but I have to go into live mode with stripe live key, it's not working in android.
If your issue is
"Request Failed", even though you could see the white window to show the cards starting to pop up, then I have the same issue.
I am in contact with Stripe support. They told me everything I have done is correct and it should be working with Stripe.
I am opening a ticket on Google Side to understand why the production isn't working. Only them can actually help now, because they will have access to the logs giving the error.
I will post here if I get any response from it
I am working on a multiplayer game using Game Kit. "auto match" is working great, but not "invite friend." The problem is that matchmakerViewController:didFindMatch: is not getting called on the invited player's device. Is there some other delegate method that I'm not seeing, which I should be using for the invitee?
I noticed in the apple docs, talking about this method, it says this:
This method is called when the view controller’s hosted property is
NO.
Is this hosted property referring to the hosting device, or that the game is hosted on a server?