I'm traying to upload the compiled ipa package to testflight via jenkins.
If I take the ipa a I send with Transporter, everything goes OK.
But when I try to do with command line, I use notarytool. Authentication goes OK, upload goes OK but it always returns status: "invalid" There is no other error description, I added -verbose command but it don't give more information.
Related
I have my own script through which I create a temporary folder for derivedDataPath. as soon as the script works and creates an IPA file, the derivedDataPath folder is deleted. But at the last stage of the build, I added a call:
Script:
${BUILD_DIR%Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run
Input Files:
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${TARGET_NAME}
${SRCROOT}/${BUILT_PRODUCTS_DIR}/${INFOPLIST_PATH}
He informs me that everything is fine and the upload will be completed in the background:
Running upload-symbols in Build Phase mode
Validating build environment for Crashlytics...
Validation succeeded. Symbol uploading will proceed in the background.
But in my IPA file creation script, the derivedDataPath folder will be deleted. Perhaps for this reason, the data is not being uploaded. How can I check the completion of the upload?
Now I have a console hanging in Firebase that there are no dSYM files for the desired version And I don't understand what's wrong with the Update not through the Appstore, but through air.
Instead of using the "run" script, you can call the "upload-symbols" script adding the --build-phase flag:
${BUILD_DIR%Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/upload-symbols --build-phase
This will make the script to upload the dSYMs as part of the build process instead of doing it in the background.
After upgrading to the latest versions of Visual Studio for Mac, Xamarin, and Xcode, I am unable to create a signed IPA archive. Everything runs on the simulator, everything builds fine in my release configuration. I can even create the archive just fine. But after I click "Sign and Distribute", regardless of whether I try to publish to the App Store or simply save the IPA to disk, I get the extremely generic "Failed to create IPA archive" message with no other detail about what failed.
As always with these types of problems, this worked the last time I tried to publish (2 months ago). Even trying to use "Sign and Distribute" on an archive I previously published successfully to the App Store fails with the same message. Are there any logs for this where I can see exactly what is failing? The Archive output window at the bottom of the screen doesn't show activity for this stage of the process.
UPDATE:
After finding the logs, was able to see the following error that shows that for some reason after upgrading the apps, permissions were somehow lost for creating the zip archive:
zip -r -y "/Applications/Xcode.app/MyApp.ipa" Payload
zip I/O error: Permission denied
zip error: Could not create output file (/Applications/Xcode.app/MyApp.ipa)
zip exited with code 15
ERROR:Failed to create IPA archive.
Finshed
So now the question becomes why, and what steps need to be taken to fix this the proper way (i.e., not just brute-forcing broad permissions)?
Are there any logs for this where I can see exactly what is failing?
To find Mac logs through:
You can select the Go > Go to Folder menu item in Finder, and then copy and paste any of these paths into the dialog.
Visual Studio for Mac
~/Library/Logs/VisualStudio/7.0 (this number may change depending on
the version you are using)
This folder can also be opened via "Help -> Open Log Directory".
If you meet the Permission denied error in the log, this may be due to saving the IPA in the XCode.App folder. You can try a different location.
If you still meet problem, you can send a feed back inside visual studio for more help.
It's very likely due to permission issue while zipping the archive.
To check if it's your case:
Open the log folder at ~/Library/Logs/VisualStudio/7.0 or in Visual Studio for Mac Help > Open Log Directory
Find and open the last log file for publishing (like Publishing.yyyy-mm-dd__hh-mm-ss.log)
Scroll to the last rows of that file. If it contains something like this (see the block below) so it's your case
zip I/O error: Permission denied
zip error: Could not create output file (/Applications/Xcode.app/YourApp.ipa)
zip exited with code 15
ERROR:Failed to create IPA archive.
Finished
In this case, once you see Output IPA file popup, just choose other save location (Desktop for example)
I am currently releasing an update for an app and i can successfully debug the project. Now when i try to archive for publishing to create the .ipa file I recieve the following error:
I have tried to delete the obj + bin folders in my iOS folder and then clean/rebuild + try again but the error still remains.
Has anyone come across this problem before? The errormessage isn't giving me much information to work with.
try to delete your current certificate in keychain and add it again.
I also faced to this same exact problem when I'm going to debug the xamarin.iOS app using Visual Studio 2015. To solve this issue, steps are as below,
Open Terminal in your Mac and type this command:
security set-key-partition-list -S apple-tool:,apple:,codesign: -s /Users /YOUR_USERNAME/Library/Keychains/login.keychain-db
Then it will prompt for your Keychain access password.
(If it repeatedly promopt that your keychain access password is incorrect, go to "Keychain Access", select and deselect the lock. Then enter your password when asked for it.
Re-enter the above command in the Terminal. Give the password.
Clean and build your project and Run it.
Now it will work definetly.
I installed the Parse Cloud Code Command Line Tools last August, and was able to update my Cloud Code regularly using "parse deploy" from the Mac OS X Terminal command line.
I am as of today on the latest Parse CLI version 3.0.1
Now today, when I try to add another Parse function to the main.js file in the "cloud" directory, and save the file, and then to a "parse deploy" I get the message "Not creating a release because no files have changed"
Indeed, the Cloud Code on the Parse.com website has not been updated.
What is my problem here?
Answering my own question... "parse deploy" did not work anymore... so I tried "parse develop", and this successfully uploaded the new JavaScript up to Cloud Code. Thereafter, "parse deploy" worked.
In summary of integration I see a link to ipa file
Environment: xcode7, mac os server 5.0.4
I can't find ipa file after success integration in post integration script.
Log from post build script:
submit Crashlytics: Crashlytics.framework/submit 1.3.5 (15)
submit Crashlytics: No file found at path /Library/Developer/XcodeServer/Integrations/Integration-54550b26ed9ba94f644c10b0691a1634/CIT.ipa
I try used the env var, like this -ipaPath "${XCS_OUTPUT_DIR}/${XCS_PRODUCT}" and got the next error
submit Crashlytics: Crashlytics.framework/submit 1.3.5 (15)
submit Crashlytics: Path must be to an .ipa file. To create an .ipa distribute an archive (ad-hoc) using Xcode.
Try this
"${XCS_OUTPUT_DIR}/ExportedProduct/Apps/${XCS_BOT_NAME}.ipa"
It's the only thing working for me.
According to this wwdc 2015 presentation, XCS_PRODUCT should produce:
Path to an .ipa or .app, if the bot produced one
But it's not working right now...
In the latest Xcode Server 5.1 version just use
"${XCS_PRODUCT}"
In Mac Server 5.2 + XCode 8.2, you have to use
"${XCS_PRODUCT}"
The path is temporary path. It will get deleted once integration complete which means finish the last post-script. So you won't be able to find anything in that path after bot completion.