djay fails to open after update to iPadOS 18.2.1

NOTE: Please use the search function above before posting to avoid creating duplicate topics.

  • Device model * iPad Air 11" (M2)
  • Version of operating system 18.2.1
  • Version of djay * latest
  • Hardware/controllers used * FLX10:

Summary of the issue:

Updated iPadOS overnight to the latest version 18.2.1, now app is failing to open

Hi @Stan_i, please close djay and follow the procedure below to perform a Forced Restart of your iPad: Force restart iPad - Apple Support

Forced Restart had no effect - app still fails to open. It shows the splashscreen with djay logo and then auto-closes.

Thanks for the update @Stan_i. I have a similar setup to you and updated to 18.2.1 and was unable to replicate this issue. Can you please try to capture a short video of the issue, upload it to your Google Drive/Dropbox, enable sharing permissions, then share a link to the video here? Thanks!

EDIT: Can you please also send me a DM with your djay account user name/email address? This will allow our engineering team and see if there are any crash reports to review. Thanks!

Thanks @Stan_i, I’ve passed this onto engineering for further review. In the meantime, if you’d prefer not to wait, you could try a fresh djay installation.

I suggest that you backup your djay Media Library database and any custom MIDI mappings, then uninstall djay, reboot your device, and reinstall the latest version of djay. You can find the files above in the following location:

  1. djayMediaLibrary: using the Files App, navigate to Locations->On My iPhone/iPad->djay->User Data
  2. MIDI Mappings: using the Files App, navigate to Locations->On My iPhone/iPad->djay
  3. Copy the files to a new location or external drive before uninstalling djay. After reinstallation, you can simply copy these files back to their original locations to maintain your Hot Cues, Saved Loops, My Collection Playlists, History and Queue.

I hope that helps!

Re-installing the app solved the issue.
Thanks!

Excellent! You’re welcome. Thanks for the follow up @Stan_i. Glad that solved the problem.