Question: Gradlew "build successful", now what? #1457
Comments
|
I also answered on the other thread, but your APK is in ./build/apk/ from your git clone directory :) You want TextSecure-release-unsigned.apk. You will have to sign it yourself. |
|
That's what Google said as well, but I don't have such a directory. |
|
|
|
Did you also run ./gradlew clean ? That command will delete your build directory. Re-run ./gradlew build and look for the folder then. |
|
Am I supposed to have a bin with the name"gradle" or is this a typo? I did not run "./gradlew clean". And I appreciate your help :) |
|
Sorry, I made a typo. You are correct- it should be ./gradlew build I would re-run the command and watch the folder. |
|
Are you on Linux or Cygwin? |
|
Turns out I am using "./gradlew" instead of "./gradlew build". Oops! Now I'm getting an error regarding not having JDK, I think I can resolve that. |
|
Do I need openJDK 6 or 7? Does it matter? |
|
I don't /think/ it matters. Try one and see. For later, here's my ./gradlew build output: signing.properties not found BUILD SUCCESSFUL Total time: 35.538 secs |
|
Thank you. The Android SDK docs mention JDK 6, I will go with that. Reference: |
|
What a disappointment, after finally obtaining an APK, my phone failed to install it. The only message is "Application not installed". |
|
Yes! That is because it is not signed. |
|
But "Unknown sources" is ticked in the settings, shouldn't that be enough? |
|
No. Android will not install an unsigned app. Unknown Sources simply means that the signer is not Google. keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -keysize 4096 -validity 10000 then jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore The build was successful, so I wouldn't worry about the build log differences. |
|
Error - "alias_name" is not a legal command. |
|
In my comment at first I typo'd the keytool command and forgot the space in "my-release-key.keystore -alias". I edited with the correct command- that typo would cause this error. |
|
Also, feel free to replace "alias-name" and "my-release-key.keystore" with names of your own choice. |
|
Also also, I probably don't have to say it, but in the jarsigner command, replace "my_application.apk" with your unsigned TextSecure apk. |
|
Your command is still incorrect, I used this instead: keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000 jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore TextSecure-release-unsigned.apk alias_name Reference: |
|
Thanks, will now test :) |
|
It worked. That was indeed a great experience. This issue can be closed. |
|
I am at a loss as to how our commands are different, aside from the RSA key size. But I am glad it worked for you :) |
|
"Sorry, this device is not supported for data messaging. Devices running versions of Android older than 4.0 must have a registered Google Account." Lol, the irony. |
|
That's what Websocket will eventually fix. Normal messaging will still work. |
|
Oh, that's good news. |
|
Unfortunately, not to my knowledge. What you can do, though, is request delivery reports for each SMS. |
|
This issue can be closed. |
|
Any ETA for Websockets? |
|
Not at the moment. You can follow the discussion here: #1000 It would appear to still be in its early stages. |
SafwatHalaby
changed the title
Hi, This is my first Android APK build. Sorry if the mistake is too obvious, it isn't for me.
I followed the instructions found here (1 to 5): https://github.com/WhisperSystems/TextSecure/blob/master/BUILDING.md
The result was this:
signing.properties not found
:help
Welcome to Gradle 1.11.
To run a build, run gradlew ...
To see a list of available tasks, run gradlew tasks
To see a list of command-line options, run gradlew --help
BUILD SUCCESSFUL
Total time: 5.701 secs
Now what? I did not get an APK.
The text was updated successfully, but these errors were encountered: