Apple often offers platform updates so as to add new options, repair bugs, and proceed to enhance the expertise for everybody who makes use of our merchandise. As a part of that course of, we provide beta software program for builders — in addition to a Public Beta Software program Program — so that individuals can take a look at their apps in opposition to upcoming software program updates, deal with pesky bugs, and share suggestions with Apple about upcoming adjustments and enhancements.
Whereas we encourage individuals to solely set up beta software program on secondary gadgets, you should still discover that a few of your prospects wish to run your app whereas utilizing a beta model of an working system. We’ve put collectively just a few suggestions that will help you take a look at and troubleshoot your apps after they’re working in a beta atmosphere, accumulate actionable suggestions from individuals, and supply suggestions of your personal.
Take a look at early, take a look at typically
As soon as a brand new beta is launched, we advocate downloading and working it on improvement gadgets as quickly as potential so as to take a look at it in opposition to your current apps. Not solely does this allow you to affirm that your app capabilities correctly, it additionally places you in an ideal place to discover the newest platform APIs and options.
The sooner you take a look at, the sooner you’ll be able to determine potential bugs, points, or regressions and flag them to Apple engineers. It’s additionally your greatest alternative to register suggestions about new options and affect future working system updates.
Triage the difficulty
Typically, adjustments to frameworks in an early beta might severely have an effect on your app. That is by no means an ideal feeling, however don’t panic! Likelihood is, a lot of your fellow builders are in the identical place.
To start out addressing the issue, first do a little bit of triage to determine what’s occurring. Is it a system situation? Is it a latent bug in your personal code? Isolate your situation by making a minimally reproducible case in a brand new Xcode mission. Once you concentrate on the code that causes the bug, you may make the issue simpler to troubleshoot — and it additionally saves you from attaching your complete app mission to a suggestions submission.
If a beta does reveal an current bug in your code, you could possibly repair it instantly and supply an replace that makes your app extra steady for each the present launch and future releases.
Typically you could possibly isolate the code in such a method you can additionally reproduce the difficulty on currently-released software program. If that’s the case and if you happen to need assistance fixing it, submit a Technical Help Incident for code-level help.
If a problem with the beta itself is stopping you from offering a repair, it’s time to file suggestions. Even if you happen to consider others have filed this bug earlier than, you must all the time ship in a report: Your copy steps and information may very well be the important thing that unlocks the issue — or pushes the difficulty to a better stage of prioritization.
Amidst all of the work you’re already doing in your app, you might be tempted to publish a blanket assertion to your web site or inside your app that you simply aren’t offering help for individuals who use beta software program. We strongly discourage this strategy: Your prospects could also be fellow builders or individuals who must run beta software program for different causes, and deterring them from working your app might make them really feel shut out — or lose belief in your software program.
As an alternative, if you happen to’re working right into a significant issue on a beta that will make for a sub-par expertise and also you gained’t be capable to deal with it in an replace, contemplate sharing your situation — in addition to the steps you’re taking to handle it — in your web site to assist inform individuals who may want to make use of your app.
Whereas individuals working beta software program gained’t be capable to depart evaluations on your app within the App Retailer, they will nonetheless present useful suggestions. Contemplate creating a simple technique on your prospects to offer bug stories — they might discover one thing you’ve missed!
Moreover, if you happen to’re struggling to repair a problem introduced on by a beta replace, contemplate reaching out to the broader developer group via platforms just like the Apple Developer Boards. Your query could possibly assist others who could also be fighting comparable challenges.
Future-proof your app
Exterior of the beta launch cycle, it’s value often evaluating your mission (and any server-side code you keep) to contemplate if there are methods you’ll be able to enhance and future-proof points of your app. A couple of inquiries to ask your self:
- Are there warnings in your Xcode mission you can repair or take away?
- Do you have got any code that depends on a selected platform or deprecated API you can replace or make platform-agnostic?
- Are you utilizing any third-party frameworks that depend on deprecated code?
- Are you able to enhance your app’s error dealing with to proceed gracefully when encountering surprising points?