Errors trying to send built to apple store connect

Mobile Beta
1

Hi!
I’m trying to send the built to apple store connect for review and I’m getting again and again unexpected error.

IMG_7189
IMG_71891125×1838 198 KB

Any help?
@nick.carroll
Thank you

2

Check your Mobile Settings > APIs, IDs, etc.

3

Thank you. That is super checked, bundle, team id, key id, issuer id, private key…I have opened a ticket a week ago but no answer, I am desperate.

4

I think there’s a problem with these keys.. Try to create new ones. I sent a new build a little while ago and it was successfully published so I don’t think there’s a problem on their part..

5

Created a new key, bundle is correct, p8 is correct, issuer id is correct, team id is correct, push notifications key and p8 is correct…can’t get to the apple store connect and create the certificate and the Provisioning Profiles

unnamed
unnamed1125×1549 131 KB

6

I would go to regenerate all the keys.. surely the problem is there somewhere..

7

Thanks. Let’s see if @nick.carroll can give us some insight into this.

8

Thanks, I have created a new bundle, renewed all the keys and still the same.

IMG_7203
IMG_72031125×1449 162 KB

9

Is your account set as an administrator in the App Store?

10

Yes, account holder and administrator

11

Mind messaging me your app id and when your last deploy was?

12

Try to remove one of your distribution certificates from Apple Developer Console and submit a new builds.

Screenshot 2025-04-15 at 12.04.14 PM
Screenshot 2025-04-15 at 12.04.14 PM2614×786 146 KB

13

If that doesn’t help, then again check the settings for push notifications. This may also be the problem.

When setting up push notifications I forgot some things, but support gave me this link, I did everything according to the instructions and oh miracle, it worked!

14

Thank you. Everything is configured correctly as far as I can tell. It just doesn’t work.

15

I thought I had everything set up correctly too, but if everything was fine, you didn’t get any errors, right? Anyway, keep posting to support more often, maybe it will help to solve the problem faster

16

Thank you very much. I have a ticket open since last week but nothing comes to fruition. I have assumed that this configuration is not necessary…

IMG_7210
IMG_72102749×2068 3.49 MB

17

Ahh everyone, please do not delete your distribution certs. We create one on your behalf the first time you do a build and if that one is deleted, you have to be manually unblocked by someone on the engineering team. The only instance where you would need to manually delete a cert is if you already have 3 in there - which would only occur if you have previously been developing ios apps not on bubble

18

I am one of those :person_facepalming:

19

I have had the same problem but even worse:

  1. I have received the apple notification about the deploy
  2. Cool went into added the new deploy and deprecated the old ones
  3. Then I got this email from bubble (after) that the deploy failed
  4. So not no OTE, now new deploy available and I had to manually remove the apple deploy + add back the people who upgraded to the NON functional apple deploy (that had a failed bubble app) behind
  5. It was two weeks ago on Saturday (two weeks ago)

So…

No ability to OTE or new deploy and I have live users in a system that I can’t support over the last two weeks… that makes me look an idiot.. in front of my client…

Support just passing email about increase priority… (I do not know what even worst cases must be in the priority list if this level of issue does not make any priority)

This mobile app is a great initiative but very broken and not managed well by the support teams… then I see new people are getting invited up and flooding the support even more…

21

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.