Create an Android Build

BlaBlu-MacBook:android-myproject BlaBlu$ ./build.sh usr/local/Cellar/android-sdk

You have authorized this computer with the ‘Enterprise (Native extensions)’ subscription.

 

Authorization succeeded.

Failure

CORONA_PATH: …/…/…/…/…/…/Applications/CoronaEnterprise

 

USAGE:  build-release.sh

USAGE:  build-release.sh android_sdk_path

USAGE:  build-release.sh android_sdk_path corona_enterprise_path

\tandroid_sdk_path: Path to the root Android SDK directory.

\tcorona_enterprise_path: Path to the CoronaEnterprise directory.

jarsigner: unable to open jar file: bin/myproject-release-unsigned.apk

./scripts/sign-release.sh: line 12: /build-tools/21.1.2/zipalign: No such file or directory

myproject.apk signed and zipaligned (with release cert)

Deauthorization succeeded.

Invalid APK file: ./bin/myproject.apk

Try:    

./build.sh /usr/local/Cellar/android-sdk

@Rob,

i tried it, uninstall the apk i have on my phone, but never creates a new one.

Invalid APK file: ./bin/myproject.apk

Regards

Can you post the messages in your terminal window?

BlaBlu-MacBoo:android-myproject BlaBlu$ ./build.sh /usr/local/Cellar/android-sdk

You have authorized this computer with the ‘Enterprise (Native extensions)’ subscription.

 

Authorization succeeded.

Failure

CORONA_PATH: …/…/…/…/…/…/Applications/CoronaEnterprise

 

USAGE:  build-release.sh

USAGE:  build-release.sh android_sdk_path

USAGE:  build-release.sh android_sdk_path corona_enterprise_path

\tandroid_sdk_path: Path to the root Android SDK directory.

\tcorona_enterprise_path: Path to the CoronaEnterprise directory.

jarsigner: unable to open jar file: bin/myproject-release-unsigned.apk

./scripts/sign-release.sh: line 12: /build-tools/21.1.2/zipalign: No such file or directory

myproject.apk signed and zipaligned (with release cert)

Deauthorization succeeded.

Invalid APK file: ./bin/myproject.apk

First time i run it was:

Authorization succeeded.

Success

CORONA_PATH: …/…/…/…/…/…/Applications/CoronaEnterprise

 

… but still Invalid APK file: ./bin/myproject.apk

What version of Corona Enterprise are you using? 

I don’t see any way for the build.sh to generate any messages about authorization.  Once you authorize once, you should need to reauthorize and I don’t know why its deauthing when it’s done.

If it ran correctly you should get multiple screens of output.

Rob

Try:    

./build.sh /usr/local/Cellar/android-sdk

@Rob,

i tried it, uninstall the apk i have on my phone, but never creates a new one.

Invalid APK file: ./bin/myproject.apk

Regards

Can you post the messages in your terminal window?

BlaBlu-MacBoo:android-myproject BlaBlu$ ./build.sh /usr/local/Cellar/android-sdk

You have authorized this computer with the ‘Enterprise (Native extensions)’ subscription.

 

Authorization succeeded.

Failure

CORONA_PATH: …/…/…/…/…/…/Applications/CoronaEnterprise

 

USAGE:  build-release.sh

USAGE:  build-release.sh android_sdk_path

USAGE:  build-release.sh android_sdk_path corona_enterprise_path

\tandroid_sdk_path: Path to the root Android SDK directory.

\tcorona_enterprise_path: Path to the CoronaEnterprise directory.

jarsigner: unable to open jar file: bin/myproject-release-unsigned.apk

./scripts/sign-release.sh: line 12: /build-tools/21.1.2/zipalign: No such file or directory

myproject.apk signed and zipaligned (with release cert)

Deauthorization succeeded.

Invalid APK file: ./bin/myproject.apk

First time i run it was:

Authorization succeeded.

Success

CORONA_PATH: …/…/…/…/…/…/Applications/CoronaEnterprise

 

… but still Invalid APK file: ./bin/myproject.apk

What version of Corona Enterprise are you using? 

I don’t see any way for the build.sh to generate any messages about authorization.  Once you authorize once, you should need to reauthorize and I don’t know why its deauthing when it’s done.

If it ran correctly you should get multiple screens of output.

Rob