At the moment, when I test and deploy an Ubuntu SDK app to the emulator/device, Ubuntu SDK creates a click package for it, named dotted.app.name_version_arch.click. This is a debug build; it has the debug policy group enabled, and its Exec line is for ./qtcdevicedebughelper.py. Both of these will cause it to (correctly) fail an app store review, because it's a debug build.
To make a release build, one must use the Publish tab of Ubuntu SDK to "Create and validate Click package" (or the equivalent command line tool). This creates a release build click package, but with the _same file name_. This makes it difficult to know which to upload to the store.
It would be useful if a clearer distinction were drawn between debug builds and release builds, in the UI of Ubuntu SDK and the filenames of created click packages. Perhaps a debug build package should be named "org.kryogenix.myapp_1.0.0_all (debug build).click" or similar? (Note: "..._all_debug.click" is not very clear; it all just looks like technical jargon.) Release builds could be "org.kryogenix.myapp_1.0.0_all (for release).click", or "...(store build)..." or similar. That way, it is a lot more obvious which click package file to upload, which it is not possible to know otherwise. It will also make clearer to developers that there is a difference between debug builds and release builds; at the moment there is no indication that these two types of builds even exist, nor that one must not be uploaded to the store and the other must be performed.
I'd very much support that, I was also bitten by this.