First thanks for the XDK update and the new CLI!
The first impression is positive although starting up takes a lot longer now....
After "converting" our main App to the new XDK format, we start building our project like we did before. Everything is working fine, the certificate manager is new and sometimes completed, but it looks like it's necessary to maintain the safety of the published apps.
In the previous versions of XDK we always did singed our App by our self (we have lost our keystore once, and we don't want to get into the same situation again). Now, with the new certificate manager, we can upload our own keystore and do it's during the build process, great!
There is only one problem: XDK is signing the app with a SHA-256 algorithm, and this algorithm is not supported on older devices (Android < 4.4). We like to support there 'older' devices too, we are using them too (and as we know: Android companies are not updating so quickly).
Is there a way to tell the XDK building systtem to use "SHA1WithRSA" signing option and not the 256 algorithm? If not we have to sign our apps by our won, like we did before....
Hello Ad -- yes, our new cert system is not signing using the older SHA1 signature but with the newer one, which is causing issues for some of the older devices. We are working on a solution in our backend, but not sure how long it will take to get that implemented. The workaround is to do what you have been doing, which is to self-sign your packages before you publish them.
I'll put a sticky note on the forum to alert others who experience the same issue.
Thanks XDK team for the new release 3357: signing works perfect now, even on older devices!
No need to use batch files any more, just click on the Build tab and wait until the compiler is ready.