forScore 12

Today we’re very happy to announce the release of forScore 12, available immediately on iOS and iPadOS as a free update for all users. If you haven’t done so already, be sure to check out our update page to learn all about it. It’s a huge update on its own, but of course that’s only the beginning—forScore 12 will be coming to the Mac this fall once Apple releases their next big update to macOS.

Thanks once again to our incredible beta testers who helped us get this major update ready, and to all of our customers for your support—it’s more important this year than ever before, and we can’t thank you enough.

forScore 12

Available now for iPad, iPhone, and iPod Touch

Apple’s Fall Updates

Each year we pride ourselves on providing optimized versions of our apps on or very near day one for each major OS update. We spend all summer working with beta versions and put a great deal of energy into ensuring that our customers have the best possible experience as soon as they’re ready to update.

Yesterday, however, Apple announced that most of this year’s updates would be released this morning. Developers were given less than 20 hours to download the finalized tools, check their apps for any bugs resulting from last-minute changes in Apple’s SDKs, and submit their apps for review (which can take anywhere from a few hours to a week or more).

Although we spent months getting ready for these updates and we’re very excited to provide our latest free update to all forScore users, Apple prohibited developers from submitting their changes until yesterday afternoon. As a result, we won’t be able to provide day-one support this year and our customers will have to wait to take advantage of the tremendous amount of work we’ve done.

Fortunately, we’re not aware of any major issues with forScore 11.2.6 running on iOS or iPadOS 14, nor are we aware of any issues with our other apps. Our recommendation in years past has been to update when you’re ready, but to consider waiting a few days or weeks if you can for any major issues to get worked out.

This year is different, though, since we’re still reeling from a significant bug in iOS and iPadOS 13.4-13.7 that Apple says has now been fixed. We still advise customers to at least consider holding off for a short while just in case something isn’t working as expected, but if you’ve been experiencing those crashes updating may be far less risky than remaining on iOS 13.

Things move very quickly this time of year, and hopefully we’ll have lots of great news to share and celebrate very soon. For now, thanks for your support and understanding.

Sneak Peek: forScore 12

forScore has come a long way since its introduction back in 2010, and what started out as a simple sheet music reader for iPad has since turned into something far bigger: the ultimate sheet music reader for iOS. Today we’re very proud to announce forScore 12, our latest major update that takes things even further.

This fall, forScore comes to the Mac with an incredible new experience that’s optimized for the big screen. It’s totally familiar but more flexible and powerful than ever, giving you a whole new way to enjoy forScore and read sheet music. forScore 12 is built for macOS 11 Big Sur and runs beautifully on all supported Macs, including the Intel-based models currently available and the Apple Silicon-powered models still to come.

As with every other major update we’ve released, forScore 12 is absolutely free for anyone who bought a previous version, and since it’s a universal purchase you get support for all three platforms automatically: iOS, iPadOS, and now macOS. That’s right, forScore for Mac is built in and absolutely free for all existing customers.

Building forScore for the Mac was no small feat, but of course that’s just part of what this major update has to offer. As usual we’ve put together a special sneak peek to give you a look at some of what’s coming. Check it out below!

forScore 12 Sneak Peek  

Labs Update

We’re continuing to test iCloud Syncing with forScore Labs, and we just dramatically increased our tester limit to allow even more people to participate. If you tried to sign up previously and weren’t able to, we invite you to check it out now. Click the button below to learn more about forScore Labs and to join the program if you’re interested.

Thank you to everyone who’s already been helping us with this—Labs’ unique testing environment has made all the difference for us as we work on this crucial component while also prepping new features and getting ready for this fall’s major OS updates. It’s a balancing act, and your patience and enthusiasm is invaluable.

forScore Labs  

iOS & iPadOS 13 Crashes

Over the past several months we’ve seen a notable increase in system-related crashes from users running iOS and iPadOS 13.4 or later. This is a system issue related to Apple’s Media Player framework that we identified and notified them about on April 6th. We’ve been doing everything we can since then to help them resolve it and they have recently indicated that this may be fixed with iOS and iPadOS 14 (we have not been able to reproduce the issue and cannot confirm this yet).

Early on, we learned that in some cases toggling the “Media & Apple Music” permissions switch in the Settings resolves the issue, but this does not work for all people. We know these crashes are unacceptable and so, given that a permanent fix appears to be some months away, we created a workaround of our own that we’re releasing today with forScore 11.2.5. Unfortunately, this bug is pervasive and the only way we can avoid these crashes is to completely avoid accessing the system’s music player—that’s a big change that reduces forScore’s capabilities, so we’re making it opt-in.

Here’s how it works: in the forScore section of the Settings app (not forScore’s own Settings panel), you’ll find a new option called “iOS & iPadOS 13.4 Workaround” that you can enable to avoid these crashes. This setting does not take effect until you restart forScore, however, so you’ll need to close and relaunch the app after you change it.

Here’s what it does: it avoids using Apple’s shared music player that forScore normally uses when it can’t play audio using its own audio engine. That means you won’t be able to view or control playback for songs currently being played by other apps (like the Music app), and you won’t be able to play songs that forScore can’t directly access. This typically includes DRMed purchases, items that are available to stream but have not been downloaded to your device, and any song if you have forScore’s “Use system audio engine” advanced option enabled.

We know these aren’t minor changes and if there was any other way to avoid these crashes without reducing functionality we would use it. For now, however, this is the best way to ensure that forScore remains stable and usable until Apple’s next major OS updates are released. We greatly value the work Apple does to improve and advance their platforms and we appreciate their help, and we want to especially thank those customers who helped us get the information Apple needed to get this bug sorted out.