I have a problem with my app.
It's currently "Pending approval".
I have accidentally submitted "Ads Management Basic Access" for review a few weeks ago and totally forgot about it. At the moment the app can't be used by people who are not testers or developers.
The problem is - i can't resubmit the app for review again. I have to mark additional features that i want the FB team to review in order for the app to be submitted for review again.
Any ideas on how to solve this? Would it be easier to just create new identical app?
Related
For my React Native app, I've pushed many builds to TestFlight in the past with no problems. I recently submitted my first actual build to the app store, and now when I'm trying to submit a new build to TestFlight, instead of going into "Testing" mode, it goes into "Waiting for review" and nothing happens. Does anyone know what I should do here? It didn't send out any invites to any of my testers or anything, and it's now been a few hours that it's been hanging in "Waiting for review" mode.
Waiting for review means that apple team will review your app before allowing you to submit on TestFlight for public testing. It will take around 24~48 hours for them to review your app. After if your app is approved, you can submit on TestFlight and create public link for anyone with the link as tester.
Did you increase your application version number? When you deploy to TestFlight the same version number but with a higher build number, it goes directly to Testing. However I noticed that changing the version number triggers a new Waiting for Review from Apple, before going into Testing
I have integrated Facebook SDK for the first time. I have submitted it to Facebook for review and its got rejected. Now let me tell you the steps I followed and the issue where I am going through.
Created an app with Facebook email, public_profile permission and went live (as its not required the review as per the document and its working fine)
Now due to change (enhancement) in the business requirement, I had to add user_friends permission also in the existing app. I have gone through many links and read about the facebook app review and Facebook test apps I have created a test app for the actual app and integrated the user_friends permission (as it works for test app)
Since the previous live app was with general permission (email, public_profile) I have not submitted this for review. So, this time I have submitted the test app for review and it got rejected (fb reviewer message
-- unable to login)
Question:
But it's still working. I am able to login properly. Cant understand what and where the problem is? I have googled for solution and found that we need to submit actual app for review. But how, the actual app is already live without user_friends permission, so in that case it will again get rejected.
Any help will be appreciated, Thanks in advance.
I have a live Facebook app that is currently used in a production website. This app has not been submitted for approval as it does not need any extended permissions.
With the upcoming feature, the app will require access to an extended permission (manage_pages). Thus I will have to submit the app to Facebook for review.
As I understand the steps to recreate the user experience has to be mentioned when submitting for review. My problem is that the new feature is not available in production until the Facebook review is complete. How will the app approval process happen as I need to list out the steps to test the app when submitting?
As an alternative I could put the app back to sandbox mode and send the review, but that would disrupt the already exiting feature (which requires the app to be live).
Is there an alternate way that I could get the app approved without having to disable any existing features?
Thanks.
As far as I found out, there is currently no way, that Facebook helps you with this.
Have you found out something?
I opened an issue in the facebook-bug-tracker:
https://developers.facebook.com/bugs/1594700337461753/
Edit:
As Facebook mentions in this bug-report, the best way for this is to mention the app-id and domain of the pre-production app to the reviewer.
I am a bit confused by this. How is Apple supposed to review in app purchase content without the app? All my IAPs are "in review" while the app itself is "waiting for review" since two days.
This is not too programming related BUT it might save other developers time to know this can happen and why. What I did:
1) Updloaded IAP content packages so I can test it.
2) Assigned IAP content packages to app, then submitted app via Xcode.
3) Found bug and rejected binary.
4) Fixed bug, resubmitted binary. But this time no way to assign the IAPs to app. They were already "waiting for review".
Did my app get stuck in a deadlock situation? Did anyone else ever experience this?
I suspect that the In App Purchases will be reviewed once your app goes into review. Your In App Purchases are already associated with the app, are they not?
However I would recommend you contact Apple through iTunes connect. I've always had good success with this in the past.
Select the 'Contact Us' link at the bottom of the iTunes connect page. In the form that appears, select App Review and Check Review Status, and then select the 'contact us' link in the text that appears.
Then describe your issue in the form, and they should tell you what you need to do.
Here is a way to fix this (its not ideal):
Delete in app purchase that is "waiting for review" in iTunes connect.
Recreate in app purchase with a different product id (you can just add a number to the end).
Refractor old references in your purchase code to the new id.
Rebuild, re-associate the product, and re-upload!
We are planning to submit our iPhone app for certification, but a friend of my suggested that if the application needs the user to login every-time to use the features, then the people at Apple would not certify the application. Can some one please guide me on this.
Its not true, you just need to provide a working username and password during the app submission so that apple can test the features.
You are definitely allowed to require a login for the app to function (I've submitted an app with multiple updates that presents a login screen as the initial dialog and locks the rest of the app until the user logs in).
You need to ensure you create a test account for the reviewer to log in with though, so make sure you provide them with a valid test Username/Password combo when you submit the app for review.
While submitting to appstore there will be option for demo account like Username/password credentials there you can give your credentials to test your application
My app was rejected for requiring a registration by the user before using any features once. I asked for a clarification on the same from the App Review team, stating that my app was based on user data, and cannot proceed without authentication. Also, I updated my review Notes in the itunesConnect to mention the same. And it was accepted. :)
For safe side, You can mention this in the review notes and do not forget to give them a sample username and password!
Good Luck!
Dontwory Your app will not be rejected by Apple. There is no restriction in apple guidelines for this. I have many live apps in app store with same scenario. So you can upload your app with worrying about app rejection.
Hope it helps you.