I deleted my iOS App from AppStore and from iTunes Connect too, but if I upload a new build from XCode's Organizer, it will update the app on TestFlight. How is that possible? I can't manage the test flight build because it isn't on iTunes Connect anymore.(can't add users for example). How do I delete the app from TestFlight?
You can expire your build in Test flight.
Related
I published my first app to AppStore last night.
I just want to know if there is code change in my app,
Should I have to re-build and upload .ipa file to itunes connect again?
(Currently, I do not use CodePush and I build app with exp)
Thanks.
Expo comes with a built in CodePush equivalent.
Whenever you publish to expo (using exp publish, the XDE etc), expo builds new JS bundles and uploads them to their servers.
Users who downloaded the app from the stores will get those updates - while iOS users will get them as soon as they open the app, Android users will get them in the second time (iOS is does this syncly while Android asyncly).
Note that this does not apply to changes in the app config (app.json), including sdk upgrades or any other configuration changes.
Yes, you will need to rebuild the release version of your app and upload to the App Store as a new version.
The news section in iTunes Connect says:
You can now create and upload apps for the App Store on Apple TV
I've tried and got this error:
I've added a new tvOS target to an existing App, which is already available in the App Store. Both targets (iOS, tvOS) are using the same bundle identifier.
Does anyone have an idea of what went wrong or has anyone been able to successfully submit a built to iTunes Connect? The error message is not helpful.
use the "Application Loader.app" of the current Xcode Beta to upload your binary.
Works for me.
I'm using the new beta version functionality in iTunes Connect. I uploaded a build (98) to iTunes Connect, set up some internal testers and they downloaded that build.
Now I've updated the build with a new version (build 99) and that's been uploaded to iTunes Connect, but I can't see how to provoke the system into pushing this new version out to the users and their TestFlight app.
I'm set up as a tester on a couple of devices (both with my developer ID as well as with another id) and I can still only see build 98.
On the iTunes Connect screen build 98 is listed as inactive (which is correct because it has been superseded by build 99), but build 99 only says 'invite testers', but I've invited all those I want to invite.
It says that users will 'automatically receive new builds', but how long does it take? I was hoping it would be instant. Is there a way to provoke iTunes Connect into sending out the update notifications so my users can test the new version?
I'm not sure if this is a bug in TestFlight but toggle off and then on again the "TestFlight Beta Testing" switch. As soon as you do it all your internal testers should get notified of the new build.
Another option is to simply go into the new Build Details and save it.
I had an app in iOS. Now I create another APP and I want to upload the same program as that other APP.
The problem is, how can Xcode knows that this program already points to the new program?
Bundle ID? App ID?
How to identify in xcode that this is the program for what program?
In other words:
How does xcode knows which app belong to the archive?
Is it by bundle id?
If I uploaded an APP and then create another APP in itunes connect, what should I do to do the itunes connect?
Short Answer is Bundle ID.
When you validate or distribute any app from Xcode to iTune it search for Bundle ID in your account and work according to that.
Your provisioning Profile have information about your Bundle ID and App ID. So set proper Bundle ID and provisioning as you do for previous app upload.
From TestFlight I get this on the build and distribution: "These teammate's devices were not identified in the embedded.mobileprovision for this build."
What do I do?
You will have to re-create the mobile profile with these devices added to it. Then, you'll need to re-build your iOS application and be sure that it is created with this new provisioning profile. Only then will these other users have access to the application (and then their devices will show up in TestFlight for that build's allowed devices).