A affable Member Licensed User Longtime User Aug 28, 2016 #1 When I try to install a release App on my real device (which I have done successfully previously) I get the "Installing..." progress Pie and it gets part way through eg 60% then restarts, over and over. Turns out it was due to Distribution instead of Development Certificates. Using #Release is no use as they are both release version, is there another way to automatically switch? Last edited: Aug 28, 2016
When I try to install a release App on my real device (which I have done successfully previously) I get the "Installing..." progress Pie and it gets part way through eg 60% then restarts, over and over. Turns out it was due to Distribution instead of Development Certificates. Using #Release is no use as they are both release version, is there another way to automatically switch?
Erel B4X founder Staff member Licensed User Longtime User Aug 28, 2016 #2 Create a new build configuration for store submissions: Code: Copy #If STORE AND RELEASE #CertificateFile: .. #End If Upvote 0
Create a new build configuration for store submissions: Code: Copy #If STORE AND RELEASE #CertificateFile: .. #End If
A affable Member Licensed User Longtime User Aug 28, 2016 #3 Erel said: Code: Copy #If STORE AND RELEASE #CertificateFile: distribution.cer #End If #If RELEASE and NOT STORE ????? #CertificateFile: development.cer #End If Click to expand... Excellent. However what conditional symbol can be used at the same time, for non-store (local device) release? Upvote 0
Erel said: Code: Copy #If STORE AND RELEASE #CertificateFile: distribution.cer #End If #If RELEASE and NOT STORE ????? #CertificateFile: development.cer #End If Click to expand... Excellent. However what conditional symbol can be used at the same time, for non-store (local device) release?
Erel B4X founder Staff member Licensed User Longtime User Aug 28, 2016 #4 You don't need to use a different certificate. Use the same one that you use for debugging. Upvote 0
A affable Member Licensed User Longtime User Aug 28, 2016 #5 Erel said: You don't need to use a different certificate. Use the same one that you use for debugging. Click to expand... I mean to switch between the distribution/store certificate, and the debug/local release certificate? Upvote 0
Erel said: You don't need to use a different certificate. Use the same one that you use for debugging. Click to expand... I mean to switch between the distribution/store certificate, and the debug/local release certificate?
Erel B4X founder Staff member Licensed User Longtime User Aug 28, 2016 #6 I'm not sure that I understand. Use the STORE build when you want to publish the app to the app store. In all other cases use the debug certificate. Upvote 0
I'm not sure that I understand. Use the STORE build when you want to publish the app to the app store. In all other cases use the debug certificate.
A affable Member Licensed User Longtime User Aug 28, 2016 #7 Erel said: Use the STORE build when you want to publish the app to the app store. In all other cases use the debug certificate. Click to expand... Ah, sorry I assumed STORE was predefined in B4i like RELEASE. I already have 6 build configurations with 100's of #if , so to duplicate each build configuration and change all the #if is not practical. Could you use the "compilation mode" combo box (like it is in B4a), as in B4i it is always locked on "debug". If you have 3 options - Debug, Local device and Store, which set predefined conditional compilation tags so they don't interfere with user created ones? Last edited: Aug 28, 2016 Upvote 0
Erel said: Use the STORE build when you want to publish the app to the app store. In all other cases use the debug certificate. Click to expand... Ah, sorry I assumed STORE was predefined in B4i like RELEASE. I already have 6 build configurations with 100's of #if , so to duplicate each build configuration and change all the #if is not practical. Could you use the "compilation mode" combo box (like it is in B4a), as in B4i it is always locked on "debug". If you have 3 options - Debug, Local device and Store, which set predefined conditional compilation tags so they don't interfere with user created ones?
A affable Member Licensed User Longtime User Aug 29, 2016 #8 Also, to share code modules between b4i and b4a, how can the "DesignText" cater for both, I can't get conditional compilation tags to work in this hidden section? - Type=StaticCode Version=2.51 ModulesStructureVersion=1 B4i=true @EndOfDesignText@ Upvote 0
Also, to share code modules between b4i and b4a, how can the "DesignText" cater for both, I can't get conditional compilation tags to work in this hidden section? - Type=StaticCode Version=2.51 ModulesStructureVersion=1 B4i=true @EndOfDesignText@
Erel B4X founder Staff member Licensed User Longtime User Aug 29, 2016 #9 affable said: Also, to share code modules between b4i and b4a, how can the "DesignText" cater for both, I can't get conditional compilation tags to work in this hidden section? - Click to expand... Please start a new thread for a new question. affable said: Could you use the "compilation mode" combo box (like it is in B4a), as in B4i it is always locked on "debug" Click to expand... B4A release option is identical to Tools - Build Server - Build release app. It doesn't matter whether it is selected in the combo box or the menu option. affable said: I already have 6 build configurations with 100's of #if , so to duplicate each build configuration and change all the #if is not practical. Click to expand... You don't need to change any code. Just create another one with the symbols relevant for store submission and also add the STORE symbol. Upvote 0
affable said: Also, to share code modules between b4i and b4a, how can the "DesignText" cater for both, I can't get conditional compilation tags to work in this hidden section? - Click to expand... Please start a new thread for a new question. affable said: Could you use the "compilation mode" combo box (like it is in B4a), as in B4i it is always locked on "debug" Click to expand... B4A release option is identical to Tools - Build Server - Build release app. It doesn't matter whether it is selected in the combo box or the menu option. affable said: I already have 6 build configurations with 100's of #if , so to duplicate each build configuration and change all the #if is not practical. Click to expand... You don't need to change any code. Just create another one with the symbols relevant for store submission and also add the STORE symbol.
