In the build configurations window it would be really helpful is we had a nother field, 'Apk Filename', where by you set the apk file name, if not set then the project name is used as is currently the case. This would mean that I would not have to change the apk file everytime I do a new build. Real world senerio, we have 3 apps that get built for MDM environments and this feature would make it more efficient.
B4A v4.30 includes a new tool named B4ABuilder.exe (and B4J includes a similar tool named B4JBuilder.exe). This tool allows you to compile your projects from the command line. This can be useful if you need to build multiple projects or to build the same project with multiple configurations...
B4A v4.30 includes a new tool named B4ABuilder.exe (and B4J includes a similar tool named B4JBuilder.exe). This tool allows you to compile your projects from the command line. This can be useful if you need to build multiple projects or to build the same project with multiple configurations...
I have elected to use the b4aBuilder as going forward I will probably have many Build configurations and a simple batch file has solved my problem. My real issue is the package name. Some of our new clients have a their own google playstore for pushing out apps to their users, and the problem is if they publish the app, no-one else can. So each customer needs their own packege name for the same app. Now if there is a more efficent way of doing this let me know.