New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appfile template #19
Comments
Sure thing: https://github.com/KrauseFx/fastlane/blob/master/lib/assets/AppfileTemplate It's a very simple file with just this 2 values. |
Thanks! It's working again :) Now I have one last issue: I suspect the code signing when building the ipa is either not happening or it's downloading the incorrect certificate. The last step breaks when uploading to itunes connect. Problem 1: The file that sigh downloaded looks correct using QuickLook (app store profile) but when I do "ipa info" it displays my team provisioning profile, along with all of the devices. Problem 2: Sigh, on startup, displays all of the 8 schemas I have in the workspace. Is it possible to hard code the schema name or number so it doesn't do that? I'm trying to automate the deployment. Great project mate :) |
Problem 1: Mh, not sure what's the problem there. Are you sure this is related to Problem 2: |
Problem 1: You are right, build settings error (in xcode) - finally managed to upload to itunes connect!! Problem 2: 'snapshot' commented out (don't need screenshots at this point). Here's the output:
|
|
|
Are you using |
|
I'm calling |
You use beta_ipa do
system("cd ..; ipa build --verbose") # customize this to build beta version
"../Mailcloud.ipa" # upload ipa file using `deliver --beta`
end which runs |
Cool thanks, I'll try looking for the answer and if not I'll create an issue there. |
It is possible (
|
Provide a better error message for when no screenshots have been taken
Hey - I've accidentally messed up my Appfile and I didn't have a previous version commited.
Can someone give me the template of the appfile with the app ide, bundle etc. so I can set my values and carry on? thanks
The text was updated successfully, but these errors were encountered: