Frequently Asked Questions
How can I check my App Factory product version?
To check the App Factory version, sign-in to your App Factory console, and then select App Factory Version from the left panel. The App Factory Version page opens, which displays the details such as the App Factory version and plugin versions.Alternatively, you can open this page by clicking the VoltMx App Factory link from the footer at the lower-right corner of the page.
Does upgrading my App Factory environment to the latest product version have any direct dependency with the Iris and Foundry versions that I am using today?
There is no direct dependency with the Iris and Foundry versions. If you upgrade your App Factory environment to the latest version, it will continue supporting and building with the Iris project version of the app, and will work with the Foundry details that were provided earlier.Can I ask the App Factory support team to install my versions of tools, software, and Jenkins plugins?
App Factory versions are tested on specific released versions of tools and plugins, so you cannot choose to upgrade any part of the configuration due to compatibility issues and security issues.However, if you notice any errors that are specific to a version of the tools that are being used in your App Factory instance, you can raise a request for assistance on the issue. You can also upgrade the tool version, if required, to resolve the issue.
What is the Xcode version that is being used in App Factory for iOS builds?
The following table lists the App Factory releases with the supported Xcode version, and the same versions are provisioned during installation or upgrade.| App Factory Release | Xcode Version Support |
|---|---|
| V8 ServicePack 4 | Xcode 10 |
| V9 | Xcode 11 |
| V8 ServicePack 2 | Xcode 12 |
| 202401 | Xcode 15 |
What kind of source control management tool is supported by App Factory?
App Factory supports most of the GIT based source code management tools such as GitHub, Bitbucket, and AWS Code Commit.What kind of build trigger can I set with App Factory?
You can create two types of triggers by using App Factory.- A cron-based trigger, which is called a Scheduler, to trigger timely builds for a project.
- A push-based trigger, which is called a Watcher, to trigger builds whenever a commit is pushed to a respective branch.
How can I cross-check the Iris version that I used in my local development, and is it the same as my App Factory build?
You can check the details that are printed in the build console log at the build job for every channel. For example:[INFO] Current Project version: 9.2.0
What is the reason for my App Factory build using a different Iris version compared to what I have used in my local development? Did I miss something?
This issue might occur if the application project is upgraded, but not pushed properly to the Git repository.After a project is upgraded or imported to a specific Iris version, build the app from Iris. If the build passes, you need to commit the diff of the workspace content code to your Git repository to trigger the build with App Factory.
Where do my Android builds occur on the App Factory build pool?
Android builds occur on a macOS agent that is hosted on a Cloud infrastructure.My build failed for some reason, how do I inspect the exact issue?
To debug a build failure, you can check the logs of a build in a project by navigating through the respective service:<project_name> → <service_name> → Builds → <build_job> → <build_number> → Console Log.For example:
TestProject → Iris → Builds → buildIrisApp → #19 → Console Log.You can also click Full Log on the Console Output page to see the whole log. You can search for ERROR statements to easily inspect the build.
In my Iris build failed scenario, what are the first key steps that I should validate before contacting the App Factory Support team?
1. Go to the build job by navigating by navigating through the respective service:<project_name> → <service_name> → Builds → <build_job>
For example: TestProject → Iris → Builds → buildIrisApp2. Click the build number of the failed build, and then click Console Output from the left panel.
3. Check the console log for any error that directly or indirectly falls under the configuration issue.
This includes validating parameters that were entered for a build and any service misconfiguration that is directly indicated.
4. In the section that contains the failed build number, you can view the logs from the Logs link in the description.
Note: This link will be available in the build description of the parent build that triggered a particular child build. Therefore, VoltMx recommends always rebuilding the parent build.
5. At least one local build must be performed on Iris by using the same source of the application for which the App Factory build failed. Make sure that you cross-verify the commit IDs on the repository and the local source.
6. In case the Iris build passes, you can share the Iris logs and app binary for debugging while raising an App Factory support ticket.
What is MustHaves logs and how do I get it?
MustHaves is a zip archive file that contains a set of log files, which are useful for debugging or analyzing build failures. These files are collected during the build process, and if the build was not completely successful, the files are shared as a downloadable link in the build history section with the label Logs.It generally contains the following set of files:
App FactoryVersionInfo.txt, environmentInfo.txt, ParamInputs.txt, irisbuildlog.log. It also contains information about the respective channel and the test-related build logs.The download links are provided if the build fails after being triggered from the buildIrisApp or buildFoundryApp page.
My Cloud account password resets every 90 days as a security policy, how can I reflect my new password in the App Factory build parameter credentials?
As per password reset policy, if you update your cloud login credentials, you need to update the same App Factory credentials that were created for the parameterFoundry_CREDENTIALS_ID.To update the credentials, navigate to the App Factory project and click the Credential link on the left panel. You can search and select the credentials from the list, click Update from the left panel, provide the new password, and then save the credentials. The builds that use this credential will use the updated password.
I carry out some manual Xcode steps during the ipa build process in my local development Mac box, will App Factory do this automatically? What should I do to get similar steps carried out in App Factory builds?
The iOS platform build takes care of standard Xcode build settings by default. If you want to execute custom steps or out of the box steps, you can do so by writing and uploading a custom hook script.Note: The hook script (automation code) must be written on your own and validated on a local Mac device before hooking it into the App Factory build pipelines.
When I triggered a build, I did not receive an email. What can cause this issue?
Make sure you have added the recipients address correctly in App Factory. For projects that use version V9SP2 or later, you can verify the recipients address in the Project Settings. For projects that use versions earlier than V9SP2, you must add the recipients address in the RECEPIENTS_LIST parameter of the respective job.App Factory only sends failure notifications from the channel level jobs to give you direct logs of the failed job for debugging. Therefore, make sure that if your build was successful, you triggered it from the main build job, such as
buildIrisApp. You can also check your spam for an email from noreply@voltmx.com.If you are sure that there is an issue with the mail delivery system of your App Factory instance, you can raise a support ticket to the CloudL2 Operations team.