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.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 years ago.
Improve this question
I am developing an iOS Enterprise application. It is same as Apple app store containing couple of my company applications. I want to know which application the users has downloaded from the app so that i can keep a track of his downloaded installations and the current installed versions on his device. I am using Swift 3.0. How should I approach for acheiving this funcationality..
Any suggestion will really help!
You cannot do this from your code out of the box. Device management is more complex in it's accessibility rights of the devices.
You need to use some kind of Mobile Device Management (MDM) software for that case. There are several services out there. Apple also has one on its own: https://support.apple.com/business
https://support.apple.com/apple-configurator
There are several other service providers available.
The link below might help you, find what you want:
As it is not really best practise posting links. If the link was broken, look for "List of Mobile Device Management Services" and you will find a bunch of alternatives to Apple's software.
http://www.pcmag.com/article/342695/the-best-mobile-device-management-mdm-software-of-2016
A short side note: I made experience with AirWatch and XenMobile so far. Get a Trial Account on their pages and check out, whether this fits your purpose and is worth the time spent to maintain the devices. Well, at last your purpose seems to me very limited to a certain request, which you could request from your user group in a different way?
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I am new in ios development. I have created one app, in this app some features are not available right now. So my question is can i submit my app to app store with same design by giving coming soon alert for those features. Thanks in advance.
It is likely that your app will be rejected if you include such an alert. Refer to section 2.1 of the App Review Guidelines:
2.1 App Completeness
Submissions to App Review should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you offer in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you explain why not in your review notes. Please don’t treat App Review as a software testing service. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.
And
2.2 Beta Testing
Demos, betas, and trial versions of your app don’t belong on the App Store...
You should remove all reference to "future functions" and put it back in when the function is available.
Yeah, as per my knowledge you can submit but it must not crash on iphone or ipad and must follow all the guidelines of apple. Because coming soon is on kind of UI of your app so i don't think that it will be rejected due to this kind of stuff.
You should refer App Store Review Guidelines for more details.
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.
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 is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We have problems releasing our Newstand App to the App Store.
It always gets rejected, because the validation of the receipts coming from the subscription In-App-Purchase seem to fail in the live (non-sandbox) environment.
The thing is, we tested everything against the sandbox environment and everything works fine. For the release version, we made sure that we use
our validation webservice that validates against the apple live-service, NOT the sandbox validation service.
So everything should work, but in the review process it always fails.
Does anyone have experience with similar problems?
Apple does test against the live-environment, right? Because we have to submit the live-Version of our App, validating against sandbox does not make sense.
We submitted the IAP items together with the App, but that should not be a problem, as the Apple testers seem to be able to purchase the subscription,
just the validation does not work.
Ok, I found sth in the Apple documentation:
https://developer.apple.com/library/ios/#technotes/tn2259/_index.html
(way down under Frequently Asked Questions 16.)
"How do I verify my receipt (iOS)?
Always verify your receipt first with the production URL; proceed to verify with the sandbox URL if you receive a 21007 status code. Following this approach ensures that you do not have to switch between URLs while your application is being tested or reviewed in the sandbox or is live in the App Store."
We misread the line above "Use the production URL http://buy.itunes.apple.com/verifyReceipt once your application is live in the App Store.", thinking Apple would use real server validation iin review process, but they also use sandbox environment.
Difficult to find this little line, they should make that fact more prominent in my opinion!
So hopefully this will resolve the issue.
Thanks for your comments though!