Presumably, anyone who has encountered this problem has dealt with it, but just in case: If you have a manifest which has
been set to read only, you'll need to unset it so that you can manually edit your app's version/release numbers prior to uploading a revision to the app store. Otherwise the release will be rejected since the version number in the manifest will not have been changed to the new version number you assigned in your B4A code.
And, of course, you need to edit the manifest manually and remember to set it to read only before compiling. Otherwise, the new version/release will get picked up, but you'll lose whatever customization your manifest needed in the first place.
been set to read only, you'll need to unset it so that you can manually edit your app's version/release numbers prior to uploading a revision to the app store. Otherwise the release will be rejected since the version number in the manifest will not have been changed to the new version number you assigned in your B4A code.
And, of course, you need to edit the manifest manually and remember to set it to read only before compiling. Otherwise, the new version/release will get picked up, but you'll lose whatever customization your manifest needed in the first place.