rfresh Well-Known Member Licensed User Longtime User Jan 5, 2019 #1 I'm using the hosted builder. How do I get to my ipa file (release build)? I don't see it on my local windows 10 PC. Do I have to access it on the hosted builder? Is there a link explaining how to do this? Thank you...
I'm using the hosted builder. How do I get to my ipa file (release build)? I don't see it on my local windows 10 PC. Do I have to access it on the hosted builder? Is there a link explaining how to do this? Thank you...
moster67 Expert Licensed User Longtime User Jan 5, 2019 #2 I haven't used B4i for a long time but if recall correctly the ipa-file should be inside the Archive.zip which you can find in the Objects folder. See this: https://www.b4x.com/android/forum/threads/publishing-your-app-to-the-app-store.57528/ Upvote 0
I haven't used B4i for a long time but if recall correctly the ipa-file should be inside the Archive.zip which you can find in the Objects folder. See this: https://www.b4x.com/android/forum/threads/publishing-your-app-to-the-app-store.57528/
rfresh Well-Known Member Licensed User Longtime User Jan 5, 2019 #3 OK thanks. I wasn't able t find that tutorial somehow. I'll go through it and see how it goes. Thanks again. Upvote 0
OK thanks. I wasn't able t find that tutorial somehow. I'll go through it and see how it goes. Thanks again.
rfresh Well-Known Member Licensed User Longtime User Jan 6, 2019 #4 I read the tutorial on creating the .ipa file. I'm getting this error message when I try to build my release version. I'm not sure what I am doing wrong. B4i Version: 5.30 Parsing code. (0.01s) Building folders structure. (0.03s) Compiling code. (0.01s) Compiling layouts code. (0.01s) Building Xcode project (0.15s) Sending data to remote compiler. Error Out: Build settings from command line: ARCHS = armv7 arm64 CODE_SIGN_IDENTITY = iPhone Distribution: Ralph Freshour (YS2F38FF3D) CONFIGURATION_BUILD_DIR = /Users/administrator/Documents/UploadedProjects/<user id>/Payload OTHER_CODE_SIGN_FLAGS = --keychain <user id> PRODUCT_NAME = DistFPM PROVISIONING_PROFILE = 2d0c0a98-caa0-4e7d-b583-fea87b9f20ae === BUILD TARGET B4iProject OF PROJECT B4iProject WITH CONFIGURATION Release === Check dependencies Code Signing Error: Provisioning profile "default" doesn't include any certificate for which the matching private key is installed in the keychain. Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.2' Error: ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Attachments keys folder.png 17.4 KB · Views: 503 keys.test folder.png 19.6 KB · Views: 504 Upvote 0
I read the tutorial on creating the .ipa file. I'm getting this error message when I try to build my release version. I'm not sure what I am doing wrong. B4i Version: 5.30 Parsing code. (0.01s) Building folders structure. (0.03s) Compiling code. (0.01s) Compiling layouts code. (0.01s) Building Xcode project (0.15s) Sending data to remote compiler. Error Out: Build settings from command line: ARCHS = armv7 arm64 CODE_SIGN_IDENTITY = iPhone Distribution: Ralph Freshour (YS2F38FF3D) CONFIGURATION_BUILD_DIR = /Users/administrator/Documents/UploadedProjects/<user id>/Payload OTHER_CODE_SIGN_FLAGS = --keychain <user id> PRODUCT_NAME = DistFPM PROVISIONING_PROFILE = 2d0c0a98-caa0-4e7d-b583-fea87b9f20ae === BUILD TARGET B4iProject OF PROJECT B4iProject WITH CONFIGURATION Release === Check dependencies Code Signing Error: Provisioning profile "default" doesn't include any certificate for which the matching private key is installed in the keychain. Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.2' Error: ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure)
Erel B4X founder Staff member Licensed User Longtime User Jan 6, 2019 #5 The provision profile and certificate do not match. Are you trying to make a store build? Upvote 0
rfresh Well-Known Member Licensed User Longtime User Jan 6, 2019 #6 No. I'm trying to make a build to release on diawi.com. Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Jan 6, 2019 #7 You should use a distribution certificate and ad hoc provision profile. Use them with both debug builds and release builds. You should only change the provision profile (not the certificate) when you want to make a store build. Upvote 0
You should use a distribution certificate and ad hoc provision profile. Use them with both debug builds and release builds. You should only change the provision profile (not the certificate) when you want to make a store build.
rfresh Well-Known Member Licensed User Longtime User Jan 6, 2019 #8 I'm still getting a release compile error (see attachment file). I changed my Release code block to this: Code: Copy #If RELEASE #CertificateFile: ios_distribution.cer #ProvisionFile: ad_hoc.mobileprovision #END IF There must be something else that I have to do? Attachments Compile Error Text.txt Compile Error Text.txt 1.1 KB · Views: 491 keys.png 17.3 KB · Views: 493 keys.test.png 21.2 KB · Views: 544 Upvote 0
I'm still getting a release compile error (see attachment file). I changed my Release code block to this: Code: Copy #If RELEASE #CertificateFile: ios_distribution.cer #ProvisionFile: ad_hoc.mobileprovision #END IF There must be something else that I have to do?
rfresh Well-Known Member Licensed User Longtime User Jan 6, 2019 #9 I created an ad_hoc provisioning file but I'm still getting this error when I try to compile a debug or a release build: Code Signing Error: Provisioning profile "ad_hoc" doesn't include any certificate for which the matching private key is installed in the keychain. Attachments ad_hoc.png 24.1 KB · Views: 521 Upvote 0
I created an ad_hoc provisioning file but I'm still getting this error when I try to compile a debug or a release build: Code Signing Error: Provisioning profile "ad_hoc" doesn't include any certificate for which the matching private key is installed in the keychain.
Erel B4X founder Staff member Licensed User Longtime User Jan 6, 2019 #10 1. You should use the same certificate and provision profile in both debug modes and release modes. Switch to a different provision profile when you want to make a store build. 2. If this error persists then delete all keys and start from scratch. Upvote 0
1. You should use the same certificate and provision profile in both debug modes and release modes. Switch to a different provision profile when you want to make a store build. 2. If this error persists then delete all keys and start from scratch.
rfresh Well-Known Member Licensed User Longtime User Jan 6, 2019 #11 i deleted all the files in \keys and keys\test. I regenerated the sign key inside B4i IDE. I downloaded my ios_distribution.cer file and my ad_hoc.mobileprovision file from my Apple developer account and copied both of those file into the keys\test folder (see attachments). I'm still getting the error below when I try to compile a debug build or a release build: Code Signing Error: Provisioning profile "ad_hoc" doesn't include any certificate for which the matching private key is installed in the keychain. How do I include the .cer file into my ad_hoc provisioning file? I must be missing a step somewhere. I'm feeling lost and confused about all of this now! Thank you... Attachments keys.png 5.5 KB · Views: 560 keys.test.png 12 KB · Views: 508 code.png 23.9 KB · Views: 475 Upvote 0
i deleted all the files in \keys and keys\test. I regenerated the sign key inside B4i IDE. I downloaded my ios_distribution.cer file and my ad_hoc.mobileprovision file from my Apple developer account and copied both of those file into the keys\test folder (see attachments). I'm still getting the error below when I try to compile a debug build or a release build: Code Signing Error: Provisioning profile "ad_hoc" doesn't include any certificate for which the matching private key is installed in the keychain. How do I include the .cer file into my ad_hoc provisioning file? I must be missing a step somewhere. I'm feeling lost and confused about all of this now! Thank you...
rfresh Well-Known Member Licensed User Longtime User Jan 6, 2019 #12 FYI -- @Jamie8763 PM'd me and offered to help so I am working with him on this. Update: I got it working now with Jamies help. Thank you very much Jamie!! Last edited: Jan 6, 2019 Upvote 0
FYI -- @Jamie8763 PM'd me and offered to help so I am working with him on this. Update: I got it working now with Jamies help. Thank you very much Jamie!!