I have been using B4A for some time, and have recently been building an app with B4i.
I have a Mac Mini (late 2014) specifically to run the B4i Builder. It is running MacOS 12.2.1 and XCode 13.2.1
My app builds OK, and works fine in the simulator, but I am having problems getting it to a physical device.
I have created a Certificate, a wildcard App Identifier (abc.*) and a Provisioning profile following Erel’s video tutorial, with the files downloaded to the Keys folder, and registered the UDID of the test device (iPhone 8)
The package name is set to abc.Lighting in Build Configuration.
I first followed Erel’s tutorial and tried creating the Bridge App, but, as I see others have reported, I get a message on the Mac asking for the B4i-Default password.
Searching other posts, I saw the suggestion was to use the Apple configurator 2.
So I then selected Build Release App, as that seemed to be the appropriate option, however at the bottom of the compile screen on the windows PC it says ‘This is a simulator Build. Do not submit it to the App Store’. It then starts running on the simulator.
I have connected the iPhone to the Mac via USB, and it is shown on the Configurator. I then Selected Add / Apps on the configurator, and found my ipa file, I selected it, and it appeared to add it to the iPhone. The correct icon appeared on the iPhone screen, however when I click on the icon, a message comes up saying ‘Unable to Install “abc Lighting” This app cannot be installed because its integrity could not be verified’
In case Configurator needed an Explicit AppID, I have also made an Explicit app id for abc.Lighting, and created a provisioning profile linking that to the certificate.
I made a separate subfolder in Keys for this explicit AppID files, changed the Keys folder in the Paths Configuration screen to this subfolder, and recompiled. I then tried to add this IPA file to the iPhone via Configurator 2, but still get the same “Unable to Install” message
I believe I have followed all the instructions, and would be grateful of any suggestions as to what I might be doing wrong.
I have a Mac Mini (late 2014) specifically to run the B4i Builder. It is running MacOS 12.2.1 and XCode 13.2.1
My app builds OK, and works fine in the simulator, but I am having problems getting it to a physical device.
I have created a Certificate, a wildcard App Identifier (abc.*) and a Provisioning profile following Erel’s video tutorial, with the files downloaded to the Keys folder, and registered the UDID of the test device (iPhone 8)
The package name is set to abc.Lighting in Build Configuration.
I first followed Erel’s tutorial and tried creating the Bridge App, but, as I see others have reported, I get a message on the Mac asking for the B4i-Default password.
Searching other posts, I saw the suggestion was to use the Apple configurator 2.
So I then selected Build Release App, as that seemed to be the appropriate option, however at the bottom of the compile screen on the windows PC it says ‘This is a simulator Build. Do not submit it to the App Store’. It then starts running on the simulator.
I have connected the iPhone to the Mac via USB, and it is shown on the Configurator. I then Selected Add / Apps on the configurator, and found my ipa file, I selected it, and it appeared to add it to the iPhone. The correct icon appeared on the iPhone screen, however when I click on the icon, a message comes up saying ‘Unable to Install “abc Lighting” This app cannot be installed because its integrity could not be verified’
In case Configurator needed an Explicit AppID, I have also made an Explicit app id for abc.Lighting, and created a provisioning profile linking that to the certificate.
I made a separate subfolder in Keys for this explicit AppID files, changed the Keys folder in the Paths Configuration screen to this subfolder, and recompiled. I then tried to add this IPA file to the iPhone via Configurator 2, but still get the same “Unable to Install” message
I believe I have followed all the instructions, and would be grateful of any suggestions as to what I might be doing wrong.