Replies: 1 comment
-
Hello, When using Fastlane for a new app, you can keep it separate from your existing app by maintaining distinct configurations, unique app identifiers, and separate certificates and provisioning profiles. Ensure each app has its own Fastlane directory and configuration files. Use unique bundle identifiers for iOS and application IDs for Android. Generate and specify separate certificates and provisioning profiles to avoid conflicts. Use environment variables or parameters to differentiate between apps in your Fastlane scripts. If using Fastlane Match, store credentials in separate repositories or branches. With these precautions, running Fastlane for the new app will not affect the existing app or its certificates. Best Regard, |
Beta Was this translation helpful? Give feedback.
-
We are currently preparing to launch a new app using Fastlane, and have successfully implemented numerous automations including the creation of certificates, provisioning profiles, p12 files, and automating the deployment process to both the App Store and Google Play etc.
At present, we have an existing app live on both the Apple and Google Play stores. As we proceed with Fastlane for our new app, we want to ensure that this new push remains completely separate, with distinct distribution and notification certificates.
Could anybody please confirm whether running Fastlane again for this new app will in any way affect our existing app or its certificates? Specifically, will Fastlane overwrite or alter the existing certificates and provisioning profiles or have a risk to break existing setups in any way?
Beta Was this translation helpful? Give feedback.
All reactions