Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
ATTENTION: Developers and Beta Testers using TestFlight
Wanted to pass a discovery on to the developers and beta testers using Testflight.
I've been beta testing a few apps lately, and one app just kept crashing... or, it would always get tossed to the background and not fully launched. It would be there to force quit out of, but you couldn't use it in the foreground and it wouldn't load into any other host.
This was not just my iPad Pro 10.5, but a few other testers. The developer was going nuts trying to track it down.
Didn't know what to tell the developer, other than this wasn't happening with anything else I had installed... and I'd already done all of the usual memory resets, hard resets, deletes, fresh installs, etc.
I had a slight hunch, that maybe it wasn't the beta build, but perhaps something to do with the TestFlight app itself. What I'd noticed is that I'd see one build number in the left hand column of Testflight, but the right panel with the app selected would show a different build number. I'd update the build number, but then I'd had to updated it again in the right panel as well. Very inconsistent too. Sometimes TestFlight would display a warning that it couldn't connect to the app store. I assumed it was more app store issues (which it could be that too).
So, I suggested to the developer that I "leave testing" of his app. Delete the beta build, delete TestFlight... reset memory, and do a hard reset. Then, reinstall TestFlight fresh... and then have the dev send me a new testing invite before downloading the app fresh.
Eureka! That worked. Solved all of the issues and is working perfectly again.
What I think was happening, was either TestFlight wasn't in fact updating the builds at all for some apps. Or, it had been corrupting the builds. I'm not a coder so that's pure speculation.
I would have shared this finding yesterday, but I wanted to go through a couple more beta build updates and make sure it all still performed consistently with no hiccups creeping back in.
If any of the developers or beta testers experience glitches, bugs, crashes that you can't quite track down... what I outlined above and maybe you'll save yourself a lot of unnecessary code sleuthing. 
Comments
Do you know if it was common to particular iPad or iOS types?
No. But I as I mentioned... I'd noticed some flakiness with TestFlight recently... maybe the last couple of weeks. We could've isolated to just my iPad, but other's were reporting the same crashes. I'm not sure exactly when it started going glitchy... but if I had to guess, it might've been around the update of 11.1.1
It's not my intent to send out any kind of alarm, etc. it's just that in this particular case... with what appeared to be a very stubborn bug to squash... it turned out NOT to be the app, but something related to the TestFlight App or Testflight platform.
That's all I know. I just wanted to pass that on to the dev/betatesting crowd so that others may be saved some time or aggravation.
Yeah good shout out
Wow.
Apple.
Get it together.
test flight does deliver bad binaries - sometimes installing over an already installed app just has unexpected functionality..... I had this on my apps and Moog model 15 betas.
Its rare though - perhaps 1 in 30?
To be fair... it could've just been a fluke app corruption from an iOS update. I remember there were 2 or 3 apps after I updated to iOS11 that got corrupted and had to be reinstalled fresh. Surprisingly few though... considering that massive update.
I'm only posting this because if developers find themselves up against a wall, stumped, and have tried everything... this is one more thing to try.
First of all, i cannot understant why anybody is torturing itself and beta testers by TestFlight, when there is such great service for direct installing beta version to iDevices just by browsing link using Safari - https://www.diawi.com
Because Testflight is usually a pretty awesome service which is completely integrated in the XCode/App Store workflow.
One way to avoid this is to avoid using 'update' on beta's and just delete the app and install it again from TestFlight.
The downside to this is that all the content created with the betas will be gone unless it's backed up first.
That's what I do 95% of the time. However, that didn't work in this case. The build was deleted, iPad hard reset, build reinstalled fresh. The ONLY thing that worked was deleting/reinstalling TestFlight. I added the "stop testing" just as an extra layer of clearing out stuff, but likely wasn't necessary.
And, I think I've said pretty much all I have to say about this at this point, unless there's some detail I left out. This wasn't to disparage any service, app, procedure, etc. The only motivation for the original post was to share an experience and something learned, so that other's may benefit from what was learned.
I'd say 99% of the time... at least from my experience, the Testflight service has been very solid.
Yes, thanks for the heads up. It's certainly wouldn't normally be the first suspect whenever a beta app doesn't run as it should
It was just painful virtually watching this developer bang his head on the wall trying to figure this one out. I so much wanted to offer something to help, but I don't know flip about coding and software builds. So many variables too.
It did feel pretty good to be of use and finally uncover the culprit that ended this poor developer soul's agony though.