Tried everything. I have typed in a verification code for ios publishing probably (no exaggeration) over a thousand times. Every SINGLE time it says “We weren’t able to verify your App Store Connect Credentials.” and gives me an error that ends up saying device not found.
Ive made new private keys. Ive copied the app. Ive switched to other app listings in my app store connect by changing the bundle id. Can someone please give me a fix for this? 17 hours!!!
I’ve been building with adalo for 4 years now and never have had anything like this happen. Submitted a support request (probably 12 hours ago) and got nothing back. Not sure what’s wrong, someone help
Adalo has been the worst platform I’ve used so far. Just last week, I successfully published a build to the App Store. The next day, after fixing some bugs, I tried to publish multiple times, only to face errors. Even after submitting a ticket, no one responded. I ended up creating a new Identifier and rebuilding everything to resolve the issue. Today, I encountered the same problem again, and honestly, I’m ready to give up on Adalo.
theres nothing better at all, this happens like once a year. Once you get through it youre good. CEO that just got hired is definitely better than the competition, i would definitely stay
Adalo updated their uptime status today (reflecting the issue) . I also got a message last night from the support team about them actively working to fix it. Lets hope they can do it soon.
Hey everyone–I apologise about the interruptions. To be completely frank, the interruption relates to how the Adalo infrastructure is set up currently, and has been on an unsustainable path. Around 1/5 of Adalo accounts were affected, because this happened in one of the clusters of infrastructure that outgrew the physical limits of what some AWS services could handle. This wasn’t a RAM or memory issue–it was an AWS hard limit that we ran headlong into, and shouldn’t have.
We’ve made some rectifications, and actually discovered quite a lot as we did so. The good news here is that the contributors to this downtime also play directly into app performance speed–which is our number one priority to fix over the remainder of the year. More rectifications are needed, but we’ve a handle on this now and are confident the interruptions won’t happen again. We’ll be taking steps immediately to restructure how the infrastructure is provisioned (thankfully the team we have now is one experienced with these overhauls) to not only avoid interruptions, but also handle performance at the same time.
For anyone that has experienced heartburn over this, I apologise and commit that we’re not doing bandaids here. We’re doing it right to do justice to what Adalo deserves–we’re ripping out the engine block and putting a Ferarri V12 engine in.
Thanks for the detailed explanation James! Great to see that you are hitting the ground running. Performance, scalability, integrations, ecosystem/community, AI and UX are key.
