techknight Well-Known Member Licensed User Longtime User Jan 9, 2019 #1 I am trying to rebuild the B4I-Bridge app. I fixed my initial issue, but I keep running into this issue: B4X: Out: Build settings from command line: ARCHS = armv7 arm64 CODE_SIGN_IDENTITY = iPhone Distribution: john doe(XXXXX) <-- removed cert identity. CONFIGURATION_BUILD_DIR = /Applications/B4iBuildServer/UploadedProjects/<user id>/Payload OTHER_CODE_SIGN_FLAGS = --keychain <user id> PRODUCT_NAME = B4i-Bridge PROVISIONING_PROFILE = 0dc3ce1b-712a-4b84-a4f3-eb02f952dc5f note: Using new build system note: Planning build note: Constructing build description Build system information error: "B4iProject" requires a provisioning profile. Select a provisioning profile for the "Release" build configuration in the project editor. (in target 'B4iProject') Error: ** BUILD FAILED ** The distribution mobileprovision file is in the Keys path. So not sure whats going on there?
I am trying to rebuild the B4I-Bridge app. I fixed my initial issue, but I keep running into this issue: B4X: Out: Build settings from command line: ARCHS = armv7 arm64 CODE_SIGN_IDENTITY = iPhone Distribution: john doe(XXXXX) <-- removed cert identity. CONFIGURATION_BUILD_DIR = /Applications/B4iBuildServer/UploadedProjects/<user id>/Payload OTHER_CODE_SIGN_FLAGS = --keychain <user id> PRODUCT_NAME = B4i-Bridge PROVISIONING_PROFILE = 0dc3ce1b-712a-4b84-a4f3-eb02f952dc5f note: Using new build system note: Planning build note: Constructing build description Build system information error: "B4iProject" requires a provisioning profile. Select a provisioning profile for the "Release" build configuration in the project editor. (in target 'B4iProject') Error: ** BUILD FAILED ** The distribution mobileprovision file is in the Keys path. So not sure whats going on there?
techknight Well-Known Member Licensed User Longtime User Jan 9, 2019 #2 Well that was painful. Things have changed as the last couple years have gone by. I had to go into the builder folder, change all the permissions recursively, and execute it as the running user instead of sudo. That fixed it. Yikes. Upvote 0
Well that was painful. Things have changed as the last couple years have gone by. I had to go into the builder folder, change all the permissions recursively, and execute it as the running user instead of sudo. That fixed it. Yikes.