I'm new to this, so please bear with me. I have an app live on the App store, developed in Xamarin. The current version is 1.0.3 and I want to keep it that way. I want to send a new build (i.e build 85) via Application loader with the same version number (1.0.3).
I want to know:
Will it become live as soon as I send it or will I have the option to keep the previous build (i.e 84) live and not this one (i.e 85)? I want the previous build (84) to be live.
Can I upload a build that I got from Ad-Hoc > iPhone => myApp.ipa / currently I'm doing this only or should I generate an ipa from a different configuration like "Release" or "App Store"?
If you try uploading your build with the same version number as your current live build, Application Loader will give you an error message saying you need to create a new app version profile in iTunes Connect.
You should be able to upload an Ad-Hoc build to ITC. However, you may need to tweak your entitlements to enable beta testing via TestFlight:
App "does not contain the correct beta entitlement"
Related
As IOS release its new updates we have IOS-11 now and to support we have Xcode9.
Xcode-9 has changes its upload process of build to i-Tunes and its quite unfamiliar for us to Follow the process.
Recently i need to upload the build but the selection of certificate section is quite confusing.
I have choose my distribution certificates but i it will not allow me to proceed further
Sometimes its says : 'Profile is not manually managed.'
Sometimes its says : Profile is not Appstore certificates.
Please if anyone can guide me How to Upload build using Xcode-9
Thanks.
I think choosing Automatically manage signing, and trying to upload a build using Application Loader will solve you problem.
I have a build server setup with Xcode 7.2 and Server 5.0.15 so we can have CI. I'm able to create an Xcode Bot that creates an archive, but it's not able to finish the last step, which is exporting the ipa archive to the Server so it can be downloaded via ad hoc builds.
I'm able to create an archive from a local machine, but whenever I run a build bot using Distribution as the scheme, I get this error...
Bot Issue for TEST-BUILD-BOT-3 (build service warning)
Integration #8 of TEST-BUILD-BOT-3
Open in Xcode: xcbot://(null)/botID/fa5f2ef869edbde2181109e01843e862/integrationID/fa5f2ef869edbde2181109e01847dbb0
Assertion: exportArchive: ipatool failed with an exception: #<Errno::EEXIST: File exists - /var/folders/3x/8t3j9vnj48530fxd4g4djp14000087/T/ipatool20160318-45875-5xq2zz/MachOs/iphoneos/armv7/(dylibs)/libswiftContacts.dylib>
File: (null):(null)
Full logs for this integration are attached.
For one thing, I'm not sure where the full logs are attached (this error is shown in the Xcode build bot window).
Some information on my project:
The project consists of an app with three extensions (share photo, share safari and watch).
I'm using Cocoapods with some swift frameworks, so I'm using the use_frameworks! keyword in my podfile.
I've tried the following:
Made sure all targets (including pods) were using the Distribution certificate.
Tried w/ and w/o Bitcode enabled.
The worst part about trying to fix this issue is that the build bot takes 20-30 minutes each time I want to test some changes I made.
Any suggestions would be much appreciated!
I had the same error, in the watchapp and watchapp extension targets, i changed the setting, under Build Settings
Embedded Content Contains Swift Code No
And the error was gone
I found this technical post from apple that says any embedded content needs to be set to No to prevent multiple copies of the swift library being added. I interpreted that as a watch target would be embedded content, (not sure if thats what they meant)
I have implemented cross platform application using Titanium 3.2.0 but when i try archiving the build for iOS AdHoc distribution, it does not get compiled. It keeps giving error with developer name as mentioned below - Invalid "--distribution-name" value ""
I tried building from XCode, Titanium UI and over Terminal as well but same error everywhere. I have referred https://jira.appcelerator.org/browse/TISTUD-5642 and it says that issue is fixed but i still face this issue over every machine updated to 3.2.0 or even when 3.2.0 is installed fresh.
Please help and provide information.
Regards.
Sounds like your Application IDs don't match from your project to your Provisioning Profile.
In your Tiapp.xml file, you may have and application id like com.mycompname.THISappname, but you told the Apple Provisioning Profile that your app id was called com.mycompname.OTHERappname. So they don't match. Change your Tiapp.xml file to match the what the Apple Provisioning Profile expects or creating another profile matching your application id in Titanium Studio.
this worked for me: create a new production certificate AND create a new provisioning profile with the same bundle ID. (Yes, this will work if you are updating an app that is already live). Download the cert and prov. profile and run both (double click). Now repeat step 6 and archive. This should work.
I am using TestFlight to distribute test versions of my app to a private group of people. As I am making a lot of updates these days I wonder if some of my testers will get sick of the large amount of update emails they receive.
So I thought it would be a better approach to let the app check for updates when started and than showing a small notification that there is a new version out and to only notify the testers about important updates by mail.
So my question is: Is there a way to retrieve information about new builds by RSS or some other channel?
Thanks.
The TestFlight iOS SDK already supports this for beta versions if you have the SDK integrated into your app:
Beta In App Updates
If a user is using a beta version of your app, you are setting the
UDID, a new beta version is available, and that user has permission to
install it; an in app popup will ask them if they would like to
install the update. If they tap "Install", the new version is
installed from inside the app.
NB: For this to work, you must increment your build version before
uploading. Otherwise the new and old builds will have the same version
number and we won't know if the user needs to update or is already
using the new version.
To turn this off set this option before calling takeOff:
[TestFlight setOptions:#{ TFOptionDisableInAppUpdates : #YES }];
I'm just trying to build my first phonegap app. So I created test AdobeID and make a successful built. But on the very same machine I need to use my company AdobeID login, but I cannot find out how to change it. Every time i run phonegap build it uses that test AdobeID that I provided in the first built.
Any ideas ?
Thanks
You should remove the project from your test ID and log in with your real Adobe ID and then upload it again from scratch, I believe.
If you are doing phonegap on mobile such as iOS, Android, you need to deactivate the test AdobeID.
Another way is to completely uninstall the app.
However, you can only activate each account 6 times. One of the limit Adobe set.