Anyone else having this issue?
Guide says to not manually create any distribution certificates and tells us to delete them to clear up spots.
I’ve only been able to successfully deploy one build and I’ve been waiting over two weeks for help from bubble support.
Any external guidance is greatly appreciated
Did you run into an issue where you didn’t have any distribution token slots available? This would have been communicated in an error message after a failed build. This is the only instance where you’d need to manually remove a cert.
All that aside, we should be handling the resetting on your behalf. This ticket is in the hands of engineering to look into next so expect a resolution soon
I deleted it after it had failed multiple times.
Builds failed anytime I had an APNs Key Id and APNs .p8 file and workflows related to push notifications
Removed all instances of this and was able to push
Tried new APNs Key ID and .p8 file and was no longer able to push any builds, but what was strange was I stopped getting emails from bubble saying my builds failed to upload and OTA updates didnt flow through to the build that we pushed to internal testers through test flight.
Tried rotating all my keys and after that I still didnt receive emails from bubble about builds and nothing showed up in TestFlight.
I then deleted the distribution certificate(only after having seen your post in April about how we shouldn’t do that-- this should really be in the official support documentation under the distribution certificate section) and only after that deletion did I start getting emails from bubble again, but this time saying the certs didnt match.
Did you also enable the Push Notification entitlement on your Bundle ID in App Store Connect? If not, that could be why it was causing issues with the build process
Are you talking about from the developer page, under Certificates, IDs & Profiles, when you navigate to identifiers → [your app’s bundle id] and select Push Notifications? If so, yes.
yes - ok good
I tried cloning app to see if you all would create a new certificate but I still got same error. Does this mean that my other mobile apps deployments will be blocked as well? @nick.carroll
You’ll have to be manually unblocked since the certificate was deleted. These certificates are linked to your account, not your app. We implemented some logic to regenerate one if it was deleted, but it seems that it isn’t working properly.
Are you in touch with success about this issue?
Yes but they’re giving me no updates like you are. Just a generic we’ll be in touch when we have more info. Literally sitting here stalled out just waiting. Been deployment ready since May. No luck on fix or good info. I understand you all are busy and I’m just one of many tickets, but starting to feel like there’s no resolution in sight @nick.carroll
Ok just asking because we are actively working on this issue and wanted to make sure that when it’s fixed, you’ll be notified through them and that we have your app on record as one of the affected apps.
And yeah apologies about the delay. There has been a big backlog leading up the the launch but we are now working through these issues a lot faster
Is a potential work around to this something along the lines of creating another account, adding new account as collaborator, changing over ownership of app, and then allowing new account to deploy the app?
Also, have you all thought about how the existing setup will work for agencies that are building mobile apps for other companies? I assume the companies they are building for would have their over Apple dev accounts. @nick.carroll
No, that wouldn’t make a difference because these things are tied to the Bundle ID and apple developer account, not the Bubble account owner/collaborators. We’ll have this fixed soon where it will be more robust
