I am maintaining an app that was previously built manually using xCode, and it is already in the App Store with all the information in iTunes Connect already set up, such as screenshots, 'what's new in this version'section, app privacy information, etc... now I've tried setting up fastlane as described in this tutorial: https://www.raywenderlich.com/233168-fastlane-tutorial-getting-started#toc-anchor-009
But I tried on a test app, which I would describe just as a sandbox that I use to train myself using fastlane. Now the question is: if I use fastlane for an app that is already in iTunes Connect, which information gets cleared and which information will stay? to be more for example: if I don't upload any screenshot with fastlane, will my previous screenshots be deleted? if I leave the default fastlane keywords, categories, etc... will they clear the previous one? I am asking to avoid the risk of losing information.
If you upload just the new build (new .ipa file without new information) you will not lose the old information.
Related
I have a tricky situation here. I have an app, where the previous developer is not available; so i can't get get an export of the certificate idenetifiers
The app already has an approved version on appstore
I would like to release an update, but as i mentioned i do not have any access to previous developer
I have so much confusion right now...
Can i remove the existing bundle in itunesconnect and recreate a new one with the same bundle id? So that i can submit a new version with the same bundle it (create certificates and stuff from scratch)
If at all i can remove, will this effect existing app in appstore?
Is there any way i can create new provisioning profiles for the existing certificates? (I tried, with the message missing private key)
Any suggestions are highly appreciated
Thanks
I'm going through a similar situation myself, some research landed me on an Apple document that reads:
"
Important: Re-creating your development or distribution certificates doesn’t affect apps that you’ve submitted to the store nor does it affect your ability to update them.
"
So, it seems to me that I can recreate the certificates and the provisioning profiles without impacting the current App or its future updates.
Here´s the link : https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html#//apple_ref/doc/uid/TP40012582-CH31-SW6
I try to upload my Mac App to the App Store, but I am in trouble with iTunesConnect since one week by now. I definitely need your kind help.
I read the Apple documentation a couple of times and asked google for a solution. I tried new Certificates and provision Profiles, a lot of build settings and - yes - I even moved to a new mac with a fresh Xcode on it. No success so far.
Here is my story: I build and run my app successfully. I subscribed to the Mac Developer Program and configured my project to sign the application for a App Store submission.
I made an archive and validated it successfully.
Then I exported the Binary like the documentation suggested and all tests passed.
Then I uploaded the archive to iTunesConnect. The archive got processed and then... I got the little triangle near the build and as I clicked onto that build, there is absolutely no information all.
Sorry I moved to a german Mac and didn't change the language to English by now
After nine builds and one week of reading and trying I have absolutely no idea how to solve that problem.
Thank you very much for every new thought.
* UPDATE *
I removed the provision profile and created a new one. Then I built a complete new Project with the same ID and uploaded it as a new build number. Again, the pre-release tab is empty.
These are my code signing settings:
Is it possible to rename an iOS app on TestFlight? The only way I see that's possible is to remove the app (and all its associated builds) and add a new one.
This is an old question, but this requirement came up today for one of our apps and thought to leave the solution for anybody who wants it.
You just need to change the Application Name in your app and upload a new build and the new name will reflect in TestFlight.
Recently I had a requirement on this. I have changed the AppName in App Information section.
Wonder if Test-flight would allows to rename the uploaded API as they have to maintain incremental build versions.
Researched a lot on this, yet Test-flight have not documented it anywhere!
One of the apps I've developed is submitted and approved to the appstore.
Because of some big changes and a more generic code I created a new XCode project for this app.
The problem is when trying to install the same app (based on bundle identifier) from the new XCode project, it quits with a crash. If I try to install again (Build & Run/Debug) from XCode, it seems to successfully overwrite and run. So it seems the first time there are some merge / overwrite conflicts. A second install, over the failed first attempt makes it work.
I wouldn't want this to happen with app updates downloaded from the store.
I've read that the idea is not to build from XCode, but use an Ad Hoc Build through iTunes instead. This would simulate a more natural end-user process. I've tried this, but somehow it won't sync / overwrite the existing app from the appstore (no errors, the app is just not changing).
Does someone have a hint on how to solve this?
Any help on this matter would be greatly appreciated!
I run into this problem all the time. I use one Developer Profile for all my dev work (and thus, one bundle identifier).
You have to delete the old App from the phone, and do a Clean Build.
These are similar problems. (1) (2)
As it seems working with an Ad Hoc build through iTunes does work.
Yesterday I double-clicked, but never got the iTunes message warning me of an older version existing in my apps and whether I want to replace it.
Dragging the .IPA into the iTunes app section did give me this message. Telling it to replace and next syncing works okay. iTunes sync status bar displays the message "YourAppName Updating". Afterwards launching it works fine with stored data intact.
The flow described here worked for me:
How to test an iPhone application update
I built a simple app that I'd like to submit to the Apple store, but I am not sure whether my project Release settings are set correctly. I adjust a few things, based on what I could find online, but I might've created more problems than I solved.
I would very much appreciate if somebody could provide a copy of working Release settings which would sure work for my project. I don't store/read any files, the application just runs a few commands. Basically, I just need it to run and install in that /Applications folder so the user could trigger a launch.
Basically use default settings, move your source code to a new project, read up the guidelines and see if anything is told to change, otherwise it's just fine. Cheers.