Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
We're building an iOS app in iOS 8 using Apple's version of TestFlight (integrated with iTunes Connect, of course). However, the system regularly refuses to send the "new build" notification e-mails to internal testers. In order to get build notification e-mails, I have to remove users from the internal testers group and re-invite them. Even when I have done this, the build notification e-mail (although it lists the desired version of the app) doesn't actually trigger an update in my TestFlight iOS app.
Points to note:
I have the Connect and TestFlight apps installed on my phone.
This has worked in the past with earlier versions of the app.
I have found other similar questions on Stack Overflow such as this and this one, but none of them seem to deal with the "this happens to me repeatedly" problem. Besides, most of them seem to suggest "remove all internal testers, disable beta testing on the app, then re-add them all" which is not a sustainable solution when we'd like to release multiple new builds per day through our continuous integration system.
Does anyone have any ideas?
ETA: I found an Apple Developer Forums thread on the subject. Not much help but it might be in future.
I had the same issue, Making changes to the "What to Test" field in the Build page and saving caused notifications to go out instantly for me.
When you upload a new build wait for a bit (I wait an hour) for all the processing to finish, then add the What to Test info and hit save. This seems to work for me quite well.
Using Edit, I removed the testers and saved. It says you can't test without testers. I added existing testers to the new build and saved. When I refreshed the page, it said they were notified with the current date.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed last year.
Improve this question
My app is rejected with the following message i don't fully understand, because there is a login and it is not Apple related. I provided the login in Resolution Center.
Guideline 2.1 - Performance - App Completeness
Specifically, we were still unable to Sign up or Sign in with Apple. Please review the details below and complete the next steps.
Review device details:
Device type: iPhone and iPad
OS version: iOS 14.4
Next Steps
Please run your app on a device to reproduce the issues, then revise and submit your app for review.
If at first you're unable to reproduce the issue, try the following:
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce.
For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
I can give you multiple options to debug and solve this problem:
https://developer.apple.com/forums/thread/651533?page=8 There is an issue with 14.4 and xcode 12 related to apple login. You can try with iOS 13 and submit video at resolution centre.
Is it due to two factor authentication ? Cross-check apple ID settings.
Try changing http to https on web server, if applicable.
Let us know which option was useful to you.
It sounds like Apple believes there is a social login (Google, Facebook, etc) included in your app. You're going to need to ensure there's not.
You've already mentioned that there's not - but perhaps there is some package you're using which includes code that triggers some automated flagging process? Review your third party dependencies.
The best thing you can do though is get more specificity from Apple. They will usually clarify rejection notices if you contact them with questions.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
Good day!
As we know in agile development we need "quick feedback" to get incremental delivery. But in iOS development it is difficult due to the long time review process.
Each submit to appstore cost us one to two weeks to wait for our app to go live.
During that period we have to start our new iteration without any online feedback and then, 2 weeks later we have to pause our development to solve online issues once the review process passed.
In this case how can we adopt agile development practice ?
No general rule that will fit all and solve all your problems, but here are some advices that will help:
Leverage iTunes Connect Testflight and your social channels to create an army of beta testers that can give you early feedback if something is terribly wrong
Dont stop development while your app is in a review, just continue working on whatever comes next and be ready to jump back to fix some issues
Prioritise app store feedback high
Don't be afraid to use expedited review feature, but again don't over use it as it will get us all in trouble.
Do user testing before actually developing features if possible
Automate testing as much as possible
These things among others will make your life easier, some of them are just best practices that can be applied in any other environment not just app store...
Good question. I think you should schedule a sprint only for "review issue" and start it only if there are some problem.
The review time it's about 4-5 days not 2 weeks I think.
Well, I use fabric to distribute my app to several beta users, make sure everything is tested as much as possible and then push application to appstore.
When you actually push your app you should be sure there will NOT be any major issues. As much as you test some small things might go by, but not major issues. Another key would be to have a team of testers that will test your app all the time.
Also, if your app is not working properly, you will get denied by Apple.
In the end, your fixes shouldn't take more then one day, or equivalent in story points.
You can define external and internal testers while using TestFlight. Since uploading a build doesn't have a review process, then you can upload a new one every-week and your testers will receive a notification each time an update is available.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
When releasing to the App Store after using iTunes Connect Testflight beta testing, what's a good way to ensure that external testers get cleanly upgraded to the official App Store version? Specifically:
Will external testers get a notification on the device that a new app version is
available? Will this be a regular iOS notification, a notification
from the Testflight app, or both?
On the home screen, will the beta app's icon show any indication that
it's been superseded by a non-beta app?
If the user has automatic app updates enabled, will the app store app
download and install automatically, replacing the beta app? Or will
the user have to upgrade manually even if auto-upgrades are enabled?
If the user opens the Apple Testflight app, will they see any
indication that the build they were testing has been superseded by a
released build?
If the answers to some of the above questions are "maybe" then what configuration or settings should we use to ensure that app updates work as expected? (where "expected" means that when we release the app to the app store, then all testers should be updated with that new version of the app).
Googling on this topic hasn't been very helpful, perhaps because Apple's TestFlight support is only a few months old so Google is dominated by non-technical news links instead of technical blogs and other places that may offer more details. I've been unable to find any programmer blogs which talk about the "upgrade from external tester to app store version" workflow.
Apple's documentation is clear about what happens from the perspective of the iTunes Connect web application (see excerpts below, coalesced for clarity) but not very clear about the external testers' user experience, which is what I'm trying to figure out. Here's excerpts from Apple's Docs illustrating this:
Finish Testing an App. To stop testing a prerelease version of an app that is actively being
tested in TestFlight beta testing, set the Testing switch into the Off
(white) position.
Submit to the App Store When you are done using TestFlight beta testing, you can submit the
app for final review. Before you submit it, make sure you no longer
want to test it or any builds you uploaded earlier than it. When the
app becomes Ready for Sale in the App Store, testing automatically
stops on earlier builds, and you will be unable to view or test them.
See When builds become unavailable for more details. If you want to
resume testing of an earlier build, you can upload it as a new build
associated with a new prerelease version.
When builds become unavailable
Before your app becomes Ready for Sale, the Prerelease pane lists all builds for all prerelease versions
you have uploaded. After the app becomes Ready for Sale, some of the
builds will be removed from the pane:
The build used in the app is removed from Prerelease, as are all other
builds in the same prerelease version. All builds in earlier
prerelease versions are also removed from Prerelease. On the
Prerelease page, the sections for those prerelease versions will be
removed.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
I'm making a game on iOS, and I'd like to know if it's possible to make a "pre-order" on my app.
Example : I want to release my game on May. Is it possible to publish it on March but just for "pre-order" ?
It's a good way to see if the app is appealing or not.
The iOS app store has no such functionality. You can only make it available or not, there is no "pre-order" status.
No, it's like "demo", "beta" policy and so on. You cannot do this in AppStore.
No, that's not possible.
You can only release apps that are fully functional.
That's why you can't release beta apps.
This is not possible. If you want to "test the waters" and/or build "hype" best thing you can do is create a landing page website with a good app description/image and see how many people are willing to leave their emails on your entry form.
Then on launch day you email blast those people.
If the app doesn't work or look like a beta, you don't have to call it a beta in the description sent to Apple. If your app is complete and good enough for Apple to approve it after it's submitted, you still don't have to release it immediately. When in the approved but unreleased state, you might be able to use up to 50 iTunes redemption codes to allow further reviewing of your app.
Before you can update the unreleased app, you might have to release it for a couple hours at 3AM in only Monte Carlo or equivalent.
You can use a service like TestFlight to release a Beta to a limited number of people (I think you can release to a max of 1000 with TestFlight)
More information on TestFlight here - http://www.testflightapp.com/
Apple inc. has strict guidelines for App submission and it review.
You can have a look at this.
You requirement for pre-order app submission violates oint 2.9: Apps that are "beta", "demo", "trial", or "test" versions will be rejected.
This link will give you more insight on the process.
So you have to either cut-short the game of yours and submit it as full-functional app. Apple doesn't care how much level your game has. And in later on-releases you can add the levels and updates. But make sure you adhere with the guidelines and do not display the "demo/trial/etc".
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
After creating Profile the status is still PENDING. How long it takes?
Its spend about 2 hour but status is still pending.
I am getting this problem first time.
Had the same issue but now it works. I tried out many things but nothing helped and I haven't seen any message about a maintenance by apple.
Apple were apparently performing maintenance for over 24 hours yesterday. There was a message:
"We are performing maintenance on the provisioning service"
Now they have removed this message and the provisioning service is still not working. It used to be immediate and as soon as your sent a request it would be done a few seconds later after your refresh the page.
I'm outraged as I actually signed up to the program again yesterday to start building an app. The iPhone simulator doesn't work for video editing for some reason and I can't deploy to to the iPhone without provisioning so I have no way to test my code.
The lack of information from Apple is ridiculous seeing as they are well aware there is a problem but have not even bothered to notify the users and have even taken down the old notice. This must be very confusing for any novice developers who are provisioning for the first time and is also severely delaying the development of my app.
I'm getting this too, It appears to be an issue with Apple. Mine has been pending for 30 minutes.
EDIT: It's fixed
Yes for me also this happened. See apple message in same page.
"We are performing maintenance on the provisioning service"
Also someone reported same issue in apple forums here.