Closed ntrpnr closed 6 years ago
After trying a local build on my Mac, I got this message:
[18-07-09 10:24:15.588] (CLI) Code Signing Error: The file "/Users/eriknilsson/projects/dottar.mobile/platforms/ios/DottarApp\DottarApp.entitlements" could not be opened. Verify the value of the CODE_SIGN_ENTITLEMENTS build setting for target "dottarmobile" and build configuration "Debug" is correct and that the file exists on disk.
It seems like Sidekick automatically added a line for DottarApp.entitlements
which is a file that does not exist. After changing the name of my entitlements file, it worked.
Is there any documentation regarding how Sidekick treats entitlement files?
Some Problem here....
https://gist.github.com/ThunderAnimal/bc393b2aa2ea6b1ca0ef2b7d4790b5c3 (release) https://gist.github.com/ThunderAnimal/c4ab90ad4a050d72924e2a69246dcf54 (debug)
Also I check the build.xconfig. The entitlements file is valid.
// You can add custom settings here
// for example you can uncomment the following line to force distribution code signing
// CODE_SIGN_IDENTITY = iPhone Distribution
// To build for device with XCode 8 you need to specify your development team. More info: https://developer.apple.com/library/prerelease/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html
DEVELOPMENT_TEAM = XXXXXXXX;
ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
ASSETCATALOG_COMPILER_LAUNCHIMAGE_NAME = LaunchImage;
CODE_SIGN_ENTITLEMENTS = behaelterMobile\behaelterMobile.entitlements
The File behaelterMobile.entitlements exists under app/App_Resources/iOS and after adding platform iOS also under platforms/ios/behaelterMobile/behaelterMobile.entitlements.
@teobugslayer
Hey @ntrpnr,
Here is the documentation that we have on entitlements. Basically, you can edit app.entitlements and Sidekick (NS CLI actually) will rename it and edit build.xcconfig for you during the prepare step of building.
Can you tell me a bit more what the setup was that got you the error - e.g. did you have your own entitlements file, what was its name, did you edit build.xcconfig yourself?
@ThunderAnimal I am a bit puzzled how you got the platforms folder file tree that I can see in the image you provided. Did you by any chance commit the platforms folder? In general, if you follow the approach from the documentation, you should be able to fix the problem. Once you make the changes to your application code, delete the platforms folder before building.
@tsvetie Thank's for your quick response. No I didn't chance anything in the platform folder. After reading the documentation, I was also quite confused where the file behaelterMobile.entitlements cames from and also the entry in the build.xconfig. I didn't make any changes in the _build.xconfig (expect the team id) and also not create the file behaelterMobile.entitlements.
So I just delete the file and the entry, removed the platforms folder and rebuild the project. Finally I got the first success build for iOS. THANKS FOR THE HELP!
Did you verify whether this issue has already been reported here?
Yes
Tell us about the problem
Cloud build for iOS fails with ** ARCHIVE FAILED **
Which platform(s) does the issue occur on?
iOS cloud build (initiated from Windows)
Provide the following version numbers that the issue occurs with:
Tell us how to recreate the issue in as much detail as possible
I have tried to do a clean build as well.
Does this issue happen every time?
Yes
Send the client logs
https://gist.github.com/ntrpnr/3a7fe0a4beeb71d628ebdafa4ce334e0