Is it possible to deploy a TestFlight build using MDM?
We'd like to deploy the app for testing with a config file.
We don't have the app in the App Store yet and want to control who can run it.
We are using a standard developer account, not an enterprise developer account.
Thanks
Related
I have a pipeline that builds an ipa and an xcarchive. Currently, I have to download the xcarchive onto my Mac and open it, distribute the app and sign it using codesign. Ideally, I would like to achieve this in an Azure Devops Pipeline. Is there an easy way to distribute the xcarchive, grab the ipa, sign it and publish the ipa to the pipeline artifact?
If you want to sign app in Azure Pipelines, you could try with the Signing and provisioning options in Xcode pipeline task.
First, you could store your Apple certificate and Provisioning Profile as the secure files in Azure DevOps.
Then, you could use the Install Apple Certificate and Install Apple Provisioning Profile tasks install them from the secure files and make them available to Xcode during a build.
When you use Xcode task, please fill the inputs for Signing and provisioning options, such as selecting the signingoptions and other details. Meanwhile, the Xcode task also helps you build the project.
After that, you could publish the build output to your pipeline artifact.
Because of incompatible changes on the backend I want to upload my app with a diffrent namespace and config to testflight for internal testing. I dont want to publish this version.
The production namespace is de.domain.app and dev is de.domain.app.dev.
How can I publish the dev version in testflight?
Do I have to create a completely new app in app store?
I am new to react native and this is my first time trying to upload the app to Testflight. I have generated ipa file for my app and I am not sure how to upload it to Testflight from Windows OS. From the expo docs, I came to know that in order to upload the app to Testflight, one has to buy monthly package of EAS and I am wondering how all the people who developed expo app uploaded it to Testflight from Windows OS. Is paying for EAS service is the only way or are they any other way to upload it?
https://expo.io/pricing
Can anyone please enlighten me? Thank you.
Apple apps needs to be submitted from macOS. You can do this
using EAS (it's uploaded from mac instances hosted by expo), there will be free tier in the future
services like macstadium or macincloud that gives you macOS instance in a cloud
fastlane + ci services like circle ci or github actions that supports macOS
I'm having trouble with the basic understanding of iOS app signing and getting these apps ready for testflight and deployment using Fastlane.
I've been to tasked to automate the deployment steps of apps we have and we have an Ionic Cordova setup currently that was used to build iOS and Android projects for 18 different apps that are currently on the app store, but I'm looking to streamline the whole process using Fastlane and I'm stumped at the Certification stages of the process.
I've no access to the existing apps private keys or know how to go about setting up the project using Fastlane as I keep receiving the errors shown below.
I've tried to follow the concepts on Fastlane Codesigning concepts, using the Fastlane projects (cert, sigh and match) and following https://codesigning.guide/ while still making no progress.
How can I go about setting up the certs on the Mac to enable it to build and push the apps to Testflight and pushing the apps fundamentally to the app store?
Thank you
Errors Recieved
Could not create another Distribution certificate, reached the maximum number of available Distribution certificates.
Could not find the newly generated certificate installed fastlane
Security find-identity -v -p codesigning return 0 valid identities found
You already have existing distribution certificates, you will have to revoke them via the developer portal or automatically via fast lane with:
fastlane match nuke distribution
BE WARNED: this will remove all certificates and provisioning profiles for distribution (development or enterprise is unaffected). Apps that are already released to the App Store and ready for sale are UNAFFECTED, this only affects packages you sign for the App Store and submit with OLD certificates, but since you have no access to them you are fine anyway.
fast lane can then create its own when you invoke it (its fairly automated).
I tested my ios app with development certificate its working when when i run an app with xcode..Later on before submission i created a distribution certificate and changed the push settings with new p12 file and distribution certificate.. pushes were unable to reach the device after that while running from xcode .. my query is
with the distribution certificate..am i able to send pushes only if the app is downloaded from app store? can't i test it by running the app from xcode before submitting?
You do need to use a distribution certificate to test the production APNS environment. You have a couple of options:
1) Create an ad hoc build.
2) Create your app store build and submit the app to TestFlight. You can then install the app with TestFlight without having to go through the app approval process. This is the best way to test production settings, APNS, CloudKit etc.
You can not debug these production builds in Xcode of course, so you may want to add some other logging etc to diagnose issues you run into.
You will have to create the IPA using the distribution certificate to test the push notifications in production environment. Its not possible to test the push notifications from the XCode build when you are signing the app with distribution certificate.