iOS 11 Compatibility

With the release of iOS 11 just around the corner, many of you may be wondering whether or not it’s safe to install. As we said last year with iOS 10, the short answer is this: if you have a recent, complete manual backup of your library and you don’t depend on forScore professionally, then go ahead and update whenever you’re ready.

The longer answer is that major updates always bring tons of big changes, from new features to behind-the-scenes refactoring that can cause all sorts of unforeseen issues (in addition to the known issues listed below). In fact, the final version Apple releases to customers will be different from any version we’ve been able to test since the first beta back in June. So whether or not you should update really comes down to this question—is there anything in iOS 11 that you need or want to try today, and could you live without forScore and your iPad for a few days? If not, wait a week and let us and others kick the tires before you jump in.

Known Issues:

Currently, there is only one bug we’re aware of that may have a meaningful impact on customers: when forScore reads a PDF page’s embedded annotations, the process of identifying links to other pages takes far longer on iOS 11 than with previous versions of iOS. This means that files with lots of links in them, especially longer files, may take noticeably longer to load or crash before finishing. If you use files with links and/or pages numbering in the hundreds, you should wait to update or disable hyperlinks in the “PDF Annotations” section of forScore’s settings panel. Unless Apple fixes this problem with a future update, working around this bug will require us to make a significant number of changes to our code and we want to be sure that they’re fully tested before we release them, so they’ll be included in a future forScore update and not the forthcoming 10.3 release.