Friday, September 12, 2014

Critical Issue When Using Spaces in Chords

At OnSong, our top-most priority is our users. We are working around the clock to address some issues that some of our users are reporting.

First, we are hearing reports and experiencing issues ourselves with the App Store. This appears to be due to changes Apple is making in preparation for iOS 8. While we've heard users having issues with the update process in the past, we are seeing an influx of installation and provisioning problems. We are trying to get in touch with Apple about these issues but have not heard back after repeated attempts.

Second, there is a crash condition happening in OnSong 1.99 caused by improperly formatted chords that include spaces in square brackets. We were able to turn around an update with an Apple-approved fix in less than 24 hours, but due to these App Store issues, the update has yet to be made available. We released the update on 9/11/2014 and it was being "Processed for the App Store" for more than 24 hours. After repeated unaddressed contacts with Apple to correct this issue, the status has been changed to "Waiting for Review", essentially starting the approval process over. We are continuing to fight for this update to be released ASAP.

View OnSong 1.991 Release Notes

If you are experiencing a crash, go into the Settings app on your device and choose OnSong under Applications. Turn on "Forget Last Song" under the Debug menu and restart OnSong. You can edit your chord charts by going into the Songs menu, tapping "Edit" and then tapping on the name of the song to "Edit Song". This will open the song editor without viewing the song. The crash is occurring if a chord in square brackets contains a space like this:

[Am on G]

Correct these errors and save. This should get you back up and running.

If the Forget Last Song option does not open OnSong, it's likely that you've received a bad installation from the App Store update process and may need to reinstall. Be sure you have a backup of your OnSong library. If not, please contact support for assistance.

We are working around the clock to resolve these issues, answer your support inquiries and do what we can to keep everyone up and running despite these challenges.

No comments: