iOS Question codesign wants to access B4i in your keychain

iCAB

Well-Known Member
Licensed User
Longtime User
Hi Everyone,

I am getting the above error while trying to configure a local mac builder on a Mac Mini running:
  1. Monterey OS
  2. XCode 13.2.1
During compile, I keep getting a popup saying "codesign wants to access B4i in your keychain" and no matter what I try, it keeps coming back.

I tried a few things, but so far unsuccessful:
  1. Using keychain,
    1. The mac user's login password doesn't work
    2. I am unable to delete the B4I certificate files
  2. I tried changing the user's password for the mac, but still getting the same results
  3. I tried deleting the keychain directly from the terminal program. The keychain was deleted and recreated on the next compile, which reproduced the same error
Any ideas?

Thanks
iCAB
 

jahswant

Well-Known Member
Licensed User
Longtime User
Upvote 0

iCAB

Well-Known Member
Licensed User
Longtime User
I don't think this is the same issue.
I am still facing the problem.
 
Upvote 0

iCAB

Well-Known Member
Licensed User
Longtime User
Does it work after you approve the dialog?

Try to start the server with sudo (sudo java -jar ...)
1. I approved the box many times- it didn't make a difference
2. using "sudo java -jar ... I am no longer getting the popup, but now I am getting the following error

B4X:
B4i Version: 7.80
Parsing code.    (0.62s)
Building folders structure.    (0.08s)
Compiling code.    (2.94s)
Compiling layouts code.    (0.00s)
Compiling debugger engine code.    (5.67s)
Building Xcode project.    (0.19s)
Preparing project for builder.    (0.41s)
    Project size: 1.51 MB
Sending data to remote compiler.    Error
Out: Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -configuration Release PRODUCT_NAME=AppName CONFIGURATION_BUILD_DIR=/Users/UserName/Documents/B4iBuildServer/UploadedProjects/<user id>/Payload "CODE_SIGN_IDENTITY=iPhone Distribution: CetificateName (7XXXXXXXX)" "OTHER_CODE_SIGN_FLAGS=--keychain <user id>" PROVISIONING_PROFILE=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -arch arm64

User defaults from command line:
    IDEPackageSupportUseBuiltinSCM = YES

Build settings from command line:
    ARCHS = arm64
    CODE_SIGN_IDENTITY = iPhone Distribution: CetificateName (7XXXXXXXX)
    CONFIGURATION_BUILD_DIR = /Users/UserName/Documents/B4iBuildServer/UploadedProjects/<user id>/Payload
    OTHER_CODE_SIGN_FLAGS = --keychain <user id>
    PRODUCT_NAME = AppName
    PROVISIONING_PROFILE = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

note: Using new build system
note: Using codesigning identity override: iPhone Distribution: CetificateName (7XXXXXXXX)
note: Planning
Analyze workspace

Create build description
Build description signature: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Build description path: /Users/UserName/Documents/B4iBuildServer/UploadedProjects/<user id>/build/XCBuildData/xxxxxxxxxxxxxxxxxxxxxxxxb-desc.xcbuild

note: Build preparation complete
warning: Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
error: "B4iProject" requires a provisioning profile. Select a provisioning profile in the Signing & Capabilities editor. (in target 'B4iProject' from project 'B4iProject')

Error: ** BUILD FAILED **


Thanks a lot for your help.
Greatly appreciated!

iCAB
 
Upvote 0

iCAB

Well-Known Member
Licensed User
Longtime User
Hi Erel.
Happy New Year!!!

Sorry for the late reply, but I tried to take a couple of days off work.

I do have a hosted builder account, but It is hard to use because of the additional library files. However, I do have an older mac that runs XCode 12.X, and all my applications compile perfectly ok, but they can no longer be uploaded to the App store.

Please let me know what should be my next step.
 
Upvote 0

iCAB

Well-Known Member
Licensed User
Longtime User
0. Server version 7.50
1. I created a small test project that has no dependencies on other libraries
2. Doesn't work. Exactly same results as reported before (with and without "sudo" )
3. Yes it does work

Thanks for your help!
 
Upvote 0

iCAB

Well-Known Member
Licensed User
Longtime User
Are you logged in to the Mac with an administrator account?
Hi Erel,

Yes, this is a fresh install and it is the only account on the mac.
I am thinking to wipe it and reinstall the OS. Do you think this could help?
 
Upvote 0
Top