Apple commonly supplies 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 folks can take a look at their apps towards upcoming software program updates, handle pesky bugs, and share suggestions with Apple about upcoming modifications and enhancements.
Whereas we encourage individuals to solely set up beta software program on secondary units, you should still discover that a few of your clients wish to run your app whereas utilizing a beta model of an working system. We’ve put collectively a number of suggestions that will help you take a look at and troubleshoot your apps once they’re operating in a beta surroundings, acquire 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 operating it on improvement units as quickly as potential to be able to take a look at it towards your present apps. Not solely does this allow you to verify that your app capabilities correctly, it additionally places you in an awesome place to discover the most recent platform APIs and options.
The sooner you take a look at, the sooner you possibly can determine potential bugs, points, or regressions and flag them to Apple engineers. It’s additionally your finest alternative to register suggestions about new options and affect future working system updates.
Triage the difficulty
Generally, modifications to frameworks in an early beta could critically have an effect on your app. That is by no means an awesome feeling, however don’t panic! Likelihood is, lots of your fellow builders are in the identical place.
To begin addressing the issue, first do a little bit of triage to determine what’s occurring. Is it a system difficulty? Is it a latent bug in your personal code? Isolate your difficulty by making a minimally reproducible case in a brand new Xcode mission. Once you give attention to the code that causes the bug, you may make the issue simpler to troubleshoot — and it additionally saves you from attaching your total app mission to a suggestions submission.
If a beta does reveal an present bug in your code, you could possibly repair it instantly and supply an replace that makes your app extra secure for each the present launch and future releases.
Generally you could possibly isolate the code in such a means which you can additionally reproduce the problem on currently-released software program. If that’s the case and in case you need assistance fixing it, submit a Technical Assist Incident for code-level assist.
If a problem with the beta itself is stopping you from offering a repair, it’s time to file suggestions. Even in case you consider others have filed this bug earlier than, you need to all the time ship in a report: Your copy steps and knowledge could possibly be the important thing that unlocks the issue — or pushes the problem to a better degree of prioritization.
Amidst all of the work you’re already doing in your app, you could be tempted to put up a blanket assertion to your web site or inside your app that you simply aren’t offering assist for individuals who use beta software program. We strongly discourage this strategy: Your clients could also be fellow builders or individuals who must run beta software program for different causes, and deterring them from operating your app could make them really feel shut out — or lose belief in your software program.
As a substitute, in case you’re operating right into a significant issue on a beta which will make for a sub-par expertise and also you received’t be capable of handle it in an replace, contemplate sharing your difficulty — in addition to the steps you’re taking to deal with it — in your web site to assist inform individuals who may want to make use of your app.
Whereas individuals operating beta software program received’t be capable of depart evaluations on your app within the App Retailer, they will nonetheless present useful suggestions. Think about creating a straightforward methodology on your clients to offer bug reviews — they could discover one thing you’ve missed!
Moreover, in case you’re struggling to repair a problem introduced on by a beta replace, contemplate reaching out to the broader developer group by platforms just like the Apple Developer Boards. Your query could possibly assist others who could also be combating related challenges.
Future-proof your app
Outdoors of the beta launch cycle, it’s price commonly evaluating your mission (and any server-side code you keep) to contemplate if there are methods you possibly can enhance and future-proof facets of your app. Just a few inquiries to ask your self:
- Are there warnings in your Xcode mission which you can repair or take away?
- Do you might have any code that depends on a selected platform or deprecated API which 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 sudden points?