Am i able to leave the Beta Entitlements in the XML descriptor for final store submission?

Forum|Forum|10 years ago
January 8, 2016
1 reply
928 views

That way I don't have to change version numbers on the last build tested... Very curious, or is this something that is not smart to do?

Development

This topic has been closed for replies.

Colin Holgate

Inspiring

No, it would fail to submit. You can delete them and do your last build using the same build version. Don't forget that your final build will be using the App Store provisioning profile, so it's a build you won't be able to test locally anyway.

X

Xpius_Sr__DeveloperAuthor

Participating Frequently

Why would it fail to submit? Its already passing submission with the Beta Entitlement. Also, I can't see you being able to keep the same build version without resubmitting another build. The Testflight version with the Beta Entitlement has to have the App Store provisioning profile. I read on another forum somewhere that you actually can submit for your final build with the Beta Entitlement in the XML... So if you're using Testflight, why not just leave the Beta Entitlement code in the XML when submitting the final build??? I truly doubt you submit another build with the removed Beta Entitlement and keep the same build number...

Colin Holgate

Inspiring

You're probably right about needing to use the App Store provisioning for Test Flight, but I have had a case where I had used Test Flight for an app, then when I uploaded it with Application Loader, it rejected it because of containing beta entitlements.

What tool are you using to build apps, that is forcing you to increment the build number each time? I don't think Application Loader cares which version you last used for Test Flight.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded