Okay, I think I got this working.
Could you please change your libversion file to say 3.2, delete all the .framework files from the Frameworks/ folder and rebuild in Xcode
Then in your Xcode project navigate to the “Frameworks” group in the navigation pane on the left. Delete the AudioKit.framework
(This won’t be necessary once Codea 3.2 is released, but you can get a head start by building against the Codea 3.2 libraries)
@Simeon, did as you suggested.
Now I have a similar error at the end of the IDEDistrbutionPipeline.log during the validate app step of the archive. This time it is for the CraftKit.
I think i have things correctly set up within my apple developer account, but i am not expert and it is quite complicated. I hope i have not screwed up there somewhere.
2020-04-23 15:45:16 +0000 Processing step: IDEDistributionCodesignStep
2020-04-23 15:45:16 +0000 Entitlements for <IDEDistributionItem: 0x7f9b9a2e6d80; bundleID=‘com.twolivesleft.CraftKit’, path=‘<DVTFilePath:0x7f9b9b4b1cf0:’/Users/paschalcoyle/Library/Developer/Xcode/Archives/2020-04-23/evtdisplay200418 23-04-2020, 17.44.xcarchive/Products/Applications/evtdisplay200418.app/Frameworks/CraftKit.framework’>‘, codeSigningInfo=’<_DVTCodeSigningInformation_Path: 0x7f9b9a10fe30; isSigned=‘1’, isAdHocSigned=‘0’, signingCertificate=‘<DVTSigningCertificate: 0x7f9ba11cc3d0; name=‘Apple Development: Paschal Coyle (6L2N8FL4ZW)’, hash=‘EED5C8382347255F9A80CF9E9AF7F7A1CDD0192D’, serialNumber=‘3B03801741081C6A’, certificateKinds=’(
“1.2.840.113635.100.6.1.12”,
“1.2.840.113635.100.6.1.2”
), issueDate=‘2020-04-17 15:10:02 +0000’‘>’, entitlements=‘(null)’, teamID=‘Y73N464VH8’, identifier=‘com.twolivesleft.CraftKit’, executablePath=‘<DVTFilePath:0x7f9b9b4dac50:’/Users/paschalcoyle/Library/Developer/Xcode/Archives/2020-04-23/evtdisplay200418 23-04-2020, 17.44.xcarchive/Products/Applications/evtdisplay200418.app/Frameworks/CraftKit.framework/CraftKit’>‘, hardenedRuntime=‘0’>’>: {
}
2020-04-23 15:45:16 +0000 Writing entitlements for <IDEDistributionItem: 0x7f9b9a2e6d80; bundleID=‘com.twolivesleft.CraftKit’, path=‘<DVTFilePath:0x7f9b9b4b1cf0:’/Users/paschalcoyle/Library/Developer/Xcode/Archives/2020-04-23/evtdisplay200418 23-04-2020, 17.44.xcarchive/Products/Applications/evtdisplay200418.app/Frameworks/CraftKit.framework’>‘, codeSigningInfo=’<_DVTCodeSigningInformation_Path: 0x7f9b9a10fe30; isSigned=‘1’, isAdHocSigned=‘0’, signingCertificate=‘<DVTSigningCertificate: 0x7f9b9ac11d50; name=‘Apple Development: Paschal Coyle (6L2N8FL4ZW)’, hash=‘EED5C8382347255F9A80CF9E9AF7F7A1CDD0192D’, serialNumber=‘3B03801741081C6A’, certificateKinds=’(
“1.2.840.113635.100.6.1.12”,
“1.2.840.113635.100.6.1.2”
), issueDate=‘2020-04-17 15:10:02 +0000’‘>’, entitlements=‘(null)’, teamID=‘Y73N464VH8’, identifier=‘com.twolivesleft.CraftKit’, executablePath=‘<DVTFilePath:0x7f9b9b4dac50:’/Users/paschalcoyle/Library/Developer/Xcode/Archives/2020-04-23/evtdisplay200418 23-04-2020, 17.44.xcarchive/Products/Applications/evtdisplay200418.app/Frameworks/CraftKit.framework/CraftKit’>‘, hardenedRuntime=‘0’>’> to: /var/folders/nl/3g6r8xf94j598_f07zh909x80000gn/T/XcodeDistPipeline.~EppFHG/entitlements~8eE6XG
2020-04-23 15:45:16 +0000 Running /usr/bin/codesign ‘-vvv’ ‘–force’ ‘–sign’ ‘E0D9EA61C759F3669A849F21BB2A64B3C02C5C1E’ ‘–entitlements’ ‘/var/folders/nl/3g6r8xf94j598_f07zh909x80000gn/T/XcodeDistPipeline.~EppFHG/entitlements~8eE6XG’ ‘–preserve-metadata=identifier,flags,runtime’ ‘/var/folders/nl/3g6r8xf94j598_f07zh909x80000gn/T/XcodeDistPipeline.~~~EppFHG/Root/Payload/evtdisplay200418.app/Frameworks/CraftKit.framework’
2020-04-23 15:45:16 +0000 /var/folders/nl/3g6r8xf94j598_f07zh909x80000gn/T/XcodeDistPipeline.~~~EppFHG/Root/Payload/evtdisplay200418.app/Frameworks/CraftKit.framework: replacing existing signature
2020-04-23 15:45:16 +0000 /var/folders/nl/3g6r8xf94j598_f07zh909x80000gn/T/XcodeDistPipeline.~~~EppFHG/Root/Payload/evtdisplay200418.app/Frameworks/CraftKit.framework: code object is not signed at all
2020-04-23 15:45:16 +0000 /usr/bin/codesign exited with 1
After some tricky detective work by myself and @Simeon we finally have the xcode export working for the validate step in the latest xcode 11.4.1. I expect simeon will send info once he has streamlined the process a bit.
@Simeon good, then i guess it must be optional!-it is not at all clear in the interface. Thanks for the privacy, based on that I submitted my first testflight today-let’s see if it works!
Wonderful!! Thank you for your effort. If possible, I would like to submit a sample zipped project in order to make sure the project works under your environment at least. Please let me the way to submit the file to you.
@Makoto you should be able to do it all yourself now. Starting from your existing exported project files in the project on your disk (not inside xcode) edit the libversion to 3.2.1. Then delete all the framework files on your disk (not inside xcode). In the xcode delete the references to the frameworks on the left side panel. Control click to get that option-do not delete the files here just the references. Then you should be able do a build. The first time will take awhile as the new frameworks will be automatically uploaded to your project. You may have add a privacy declaration for the camera in the info.plist. Currently it will not work with the simulator, but you should be able to build and upload to a connected device or make an archive for the app store connect.
@Simeon even for a testflight submission, the app store connect seems to imply we need to provide a license agreement. Is that the case or is only if you want a license agreement different than some default license? If i really need to supply a license agreement, could you suggest one i could start from and adapt?
@piinthesky do you mean privacy policy?
@Makoto if you export from Codea 3.2.1 you should be good to go, but yes you will need to add the privacy usage descriptions
@Simeon Thank for your effort to fix the issue. Now I can make an archive and submit to apple store a zipped project with Codea 3.2.1 under iOS 13.4.1. In order for archiving in Xcode, since building for simulator gives an error, I need to connect a device to build the project to enable the archiving function.
Thus the ultimate problem was cleared, I just want to clarify the method you suggested for a project zipped with Codea 3.1.
You mentioned " In the xcode delete the references to the frameworks on the left side panel. Control click to get that option-do not delete the files here just the references. ", but I can not find ‘delete reference only’ option other than “Delete” (file) option. I don’t see any changes with “Control key” in the option list with mouse button click.
Please tell me more about the way to delete reference.
Without this step, the zipped file with Codea 3.1 gets an error in building for a connected device?even Frameworks folder has only one file, libversion whose content is “3.2.1”.
@Simeon one has to provide a url for the privacy policy, but there is also a place to add a license agreement text in the testflight submission.
@piinthesky I’ve never provided a license agreement, but we do provide a Codea privacy policy here: https://codea.io/privacy
@Makoto I had to remove the simulator functionality, as Apple will not accept binaries that contain simulator slices. Sorry for this. Looking for a work around, but until then you must test on device
Hmm I think that advice may have been relating to something else. To delete references in Xcode you simply delete a file in the left pane, then it will ask do you want to “Delete References” or “Move to Trash”. In the case of the Codea frameworks for 3.2.1, if you need to upgrade them, you should delete them from the Frameworks/ folder in Finder and leave the Xcode project as-is
@Simeon Thank you. Finally, I could go through validation process to send my app to App store by;
I expect 2) and 3) above as well as the use of simulator are fixed in the next version on order to make Codea compatible to Xcode.
Regarding “Delete reference” issue, my Xcode dose not ask if I want to “Delete References” or “Move to Trash” but just delete (maybe trash) the files when I choose “Delete” option in the pull down menu of the options.
?Simeon, I moved forward next step to invite external tester for TestFlight for my app coded with Codea 3.2.1. I submitted request for approval but Apple rejected for two reasons; use of ARKit and True Depth API.
I don’t use those features but they are equipped in Codea 3.2.1.
I have never encountered such rejection for the apps coded with Codea 2.x.
Please instruct me how to avoid the rejection.
–Rejection letter from Apple --------------------------------------
2020?5?6? 4:59
???: Apple
2. 1 Performance: App Completeness
2. 5 Performance: Software Requirements
Guideline 2.1 - Information Needed
We have started the review of your app, but we are not able to continue because we need additional information about your app.
Next Steps
To help us proceed with the review of your app, please provide detailed information to the following questions. The more information you can provide upfront, the sooner we can complete your review.
Once you reply to this message in Resolution Center with the requested information, we can proceed with your review.
Guideline 2.5.1 - Performance - Software Requirements
During review, we found that your app includes TrueDepth APIs. However, we were not able to locate any features in your app that use TrueDepth APIs.
Next Steps
If your app does not include any features that use TrueDepth APIs, please remove them from your app.
If your app does include features that use TrueDepth APIs, please reply to this message in Resolution Center to provide information on how to locate them.