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.
Comments
Yeah, as I noted above, issue is happening on my iPad and iPhone both with 12.3.1, but funnily, it works on my old iPhone 5s with iOS 8.3
@wim, do you have a case number? Maybe if people start linking and referencing other cases it will help - I'm on the phone and the guy "hasn't heard about this issue"
BTW, chatter on other forums is that it's somehow related to TestFlight. Haven't had time to investigate....
As I mentioned before, I suspect that it's somehow related to the Apple ID, since that's the only commonality between my iPad Pro 12" and my wife's iPad Air 2
If this IS related to Testflight as previously mentioned has anyone deleted Testflight to see if that fixes it?
I will try that later when I get home from work
It happens on devices that don't have Testflight installed too. But, I do have Testflight in use on my account on other devices, so maybe there's something there that gets flagged on the Apple ID.
Case # 100952773255
It hasn’t started happening to me (knock wood). I use Test Flight.
Based on what people are reporting, it sounds like some backend upgrade has had an impact and that Apple hasn’t heard from enough people yet to realize that this isn’t a user-error type situation...which means that the tech support people are doing their best but not able to solve the problem — whose cause may not yet be recognized. The backend is enormously complicated. Probably some minor change somewhere had unintended consequences.
Mine is case #100953276028
Just finished my call; nice Tier 2 support guy, but no new ideas. This is clearly a back-end issue.
My case is: 100956622251
I would suggest others call in and reference those case numbers.
I emailed the case numbers to the person who is to call me in three hours. Maybe that'll help.
Did the same as well as sending several discussions on the issue:
https://discussions.apple.com/thread/250852309
https://discussions.apple.com/thread/250852507
https://discussions.apple.com/thread/250864413
https://discussions.apple.com/thread/250873260
https://forums.macrumors.com/threads/merged-ios-13-2-2-app-updates-stuck-on-waiting.2210793/
@aplourde, cool. Thanks, sent those over as well.
Apple support called me back within 30 minutes, two hours before the scheduled call, to tell me they had referred it over to engineering. Took me three weeks to get to this point last time. Huge improvement!
From what I've read on other forums and twitter feeds from people having this same problem... it doesn't appear to be related to any specific IOS version. There are some still running 12 with this problem too.
There was an interesting detail that might be something... it appears that a common factor seems to be those who either have a dev (sandbox) account or a TestFlight account AND have made a purchase via the beta app... the kinds of purchases that you aren't actually charged for like IAPs that are only good within the beta app.
Is that a common factor in this thread among those who're experiencing this problem? It is for me.
I've read that those who have this issue have it on all devices signed into their particular Apple ID. And I've also read some who've gone to the extreme of completely wiping their device... installing a new OS, and then after signing back in using the same Apple ID, the problem remains.
Some have reported signing out with their Apple ID and signing back in with a spouse's Apple ID that's not having the problem... and the problem goes away until they sign back in using the allegedly/corrupted Apple ID.
Definitely.
I do use TestFlight, but I've never made any purchases via the beta app.
Not for me.
I have done all of this, and even more the last time around. None of those steps fixed it. The same day it was finally "referred to engineering" it finally started to work. This time around I've gotten that engineering referral quicker than last, so I'm hopeful.
That was one of the steps Support had me go through this time. Yes, that is the behavior that I've verified.
Yep - I use Testflight and have downloaded IAPs from within a beta-version.
Yeah - they asked if I had access to another Apple ID but we all share mine in the house for simplicity, so I couldn't test this.
Yes, I have two devices on 12.3.1 with this issue; however I have an old iPhone 5s on 8.3 that can update just fine....
Yes, I'm in that boat - beta testing Audiobus with the MIDI learn IAP activated.
The iPhone 5s is signed in to the same AppleID as the other devices, so it's not just based on the ID per se.
That said, I don't think I have TestFlight on the 5s (can't remember off hand and it's not with me right now).
It doesn't fix anything. But in my case, it helped move the process along. You wouldn't believe all the things I did last time on a spare device to get them to refer it to engineering. That's a little process I fondly refer to as "eliminating what it's not". Unfortunately that's sometimes the only troubleshooting process that works ... until the case gets into the right hands. It can be a long process to get there. Thankfully it's moving faster this time.
By the way... I don't have any answers. I've done pretty much ALL of the checking the time, reset network, sign out of icloud, sign out of Apple ID, hard resets, etc. etc. I've done pretty much every suggested thing except for a complete wipe and reinstall fresh.
My guess is that there's nothing I can actually do and that when it hopefully is eventually fixed... it won't be in the form of an update but something Apple has to fix on the backend.
I did notice that BEFORE I updated to IOS 13.2.3 that introduced this app update problem... the app store updates had already been weird for a couple weeks. I'd have about 20 updates... update them all. Then later that evening or the next day, most of those same apps would need to be updated again. As if the update didn't actually take the first time.
Mine started last week before the 13.2.3 update so while the update might have triggered this for some people, not foe me.
Well, there are more ways than one this could play out. If it's a system background fix then hopefully all affected users are fixed at once. If it's localized to certain servers or networks then some may be fixed and others not until support cases trigger specific investigation. If it's localized to certain Apple IDs, then it might take each and every person pursuing it with Apple support.
Given that last time it was seemingly only my Apple ID, and I never saw another report of it, it is possible that it's not a system wide thing. The fact that it's happening to lots of people is actually encouraging against that though.
Anyway, we'll all start to see whether it goes away for everyone or if it requires follow-through with support soon. Hopefully.
So my case was closed, but here's the case number in case you all want to reference it in your cases:
Case ID: 100956082250
Yeah, I've considered the possibility that they'll only bother fixing the accounts of individuals. I'm trying to be hopeful though.
I have seen more and more reporting this on twitter, forums, etc. so... maybe the hope for a complete fix isn't entirely in vain. Fingers crossed.
I haven't had an update on my Catalina machine that used the same Apple ID since this first occurred for me. You'd think that if it was a corrupted Apple ID that it would effect a desktop install using that same Apple ID. Has anyone experienced this same problem spreading over to an macOS machine?
I'm leaning toward the TestFlight connection. However, it's curious that my TestFlight updates still update fine. Is there anyone here with this app update problem who has never used TestFlight with the associated Apple ID experiencing the issue?
Well, well, well. Just like last time. A few hours after finally getting support to escalate the case to engineering ... my updates are finally installing again.
I’m gonna try like hell again this time to get them to tell me what they fixed. Not much hope on that point, but I have to try.
Mine are downloading now too so if you sent those case #s they must have flipped the switch for all of us.
Mine just started working too. Halle-freakin-lujah!!!
I couldn't update any apps 2 days ago. Yesterday is was working fine. Today not working again, says "Try again later"
That’s a different issue. Probably just the App Store temporarily overloaded or something. Nothing to worry about.
Mine have just started working again as well
+1,000 .. Mine too!! Finally!