I am new to using calabash-android to test Android applications.
What does the calabash-android resign name-of-my.apk do?
Thanks
The resign is used if you need to sign the app to match your keystore.
Copied from GitHub docs https://github.com/calabash/calabash-android/wiki/Running-Calabash-Android
Instead of resigning you could also consider copying your debug keystore to your folder.
The apk calabash android runs must be signed with the same keystore as
the test-server.
Use the command: calabash-android resign to resign your
application.
Building the test-server using calabash-android build will build
the test-server and sign it with the same key as the application you
are testing.
Related
after build expo, i released at play store.
After this i installed dependency to add useful function.
("react-native-draggable-flatlist")
is it possible to publish?
If this is not possible, I have to remake apk.
oh, and if i built expo(making apk file), can i publish?
I didn't take any action before build.
yes you can after building expo released apk
If you make any of the following changes in app.json, you will need to re-build the binaries for your app for the change to take effect: Increment the Expo SDK Version Change anything under the ios, android, or notification keys Change your app splash Change your app icon Change your app name Change your app owner Change your app scheme List item Heading
see the doc here
I created one application using Ionic2 and when i run the command ionic cordova run android --prod --release I am getting an error
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES: Package /data/app/vmdl
971492117.tmp/base.apk has no certificates at entry AndroidManifest.xml]
Do anyone know how to fix this error?
NB: I have seen similar questions all of them are for native application development.
You cannot install a package build with --release without signing it. See this question on Ionic Forum
Try ionic cordova run android --prod to install an unsigned app to your phone.
Probably you have another app installed with the same name, signed with another type of key. Ie in your device you the app singed with a release key. Other possibility is there is an app in your device with a newer version.
I am starting a Django project. I'd like to connect this project in such a way my partner could work remotly and we can see the trackings and modifications on that project. What do you suggest to set up those configurations?
The program is called git, its not necessary use GitHub, Bitbucket to deploy your Django project in a server, also you can have a version control of your project and work with your patner without problems. Read this to deploy your Django project https://www.digitalocean.com/community/tutorials/how-to-use-git-hooks-to-automate-development-and-deployment-tasks#using-git-hooks-to-deploy-to-a-separate-production-server and this is git https://git-scm.com/
We need a quick help. We were trying to automate our Andriod mobile app using calabash. We have grown through all your related tutorials but can't succed in real scenario.
We did following for our app:
Installed Ruby, Android SDK, JDK, Calabash on Windows 8.
jdk - jdk-7u51-windows-x64
RUBY - rubyinstaller-1.9.3-p545
sdk - fOR 64 BIT
Set Environment variables:
ANDROID_HOME - C:\Users\Dinesh\Desktop\Calabash\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
JAVA_HOME - C:\Program Files\Java\jdk1.7.0_51
Connected Samsung S3 Andriod device to USB (USB Debugging = Checked)
Open eclipse and run Emulator
I can see my connected device by running ADB DEVICES command.
ISSUES:
A. Though we have JDK installed, we always get "JAVA DEVELOPMENT KIT Could not" error message while resigning apk file. How to get rid of this message?
B. Real android device (connected to the USB) is not showing up in the emulator and also in the Android Virtual Device Manager list?
HOW TO INSTALL CALABASH FOR ANDROID IN WINDOWS
Steps to follow:
Download Ruby.exe with version less than 2.0 (In this tutorial I am going to use rubyinstaller-1.9.3-p545.exe)
Download Ruby Development Kit (For use with Ruby 1.8.7 and 1.9.3)
Create a folder called DevKit in C:\DevKit
Extract Ruby Development Kit (DevKit-tdm-32-4.5.2-20111229-1559-sfx.exe) to C:\DevKit
Open command.exe or cmd.exe and type ruby -v to check ruby version(ruby 1.9.3p545 (2014-02-24) [i386-mingw32])
Now type: cd C:\DevKit and press enter
Then type: ruby dk.rb init
Then type: ruby dk.rb install
Then change to Ruby193 directory by typing: cd C:\Ruby193 on cmd
Type: gem install calabash-android
Type: gem install calabash-cucumber
check by typing: calabash-android version
In order to test you *.apk file in calabash you need to re-sign it
So to make it work you can use two options
Option 1:
Type: calabash-android resign *.apk and press enter
Type: calabash-android build *.apk and press enter
or
Option 2:
Use a .jar file called re-sign.jar
Then create a folder called sample in your desktop and place *_debug.apk. Open cmd then change directory where the *_debug.apk file is found and type: calabash-android gen , to generate the feature files and other associated resources.
Last you need to type: calabash-android run *_debug.apk to run the application
Note: To run the application you can use emulator, android device, android screen cast or any related software or devices that allows you to view the process.
I have just downloaded cakephp latest version 2.3.0 and trying to create skeleton application
using bake command.
Problem is when I execute the command cake bake at /app>cake bake. Following message I am getting:
Welcome to CakePHP v1.3.2 Console
App : app
Path: /var/www/cake-acl/app
Your database configuration was not found. Take a moment to create one.
Database Configuration:
You can see, console is showing Cakephp version 1.3.2, even I have downloaded 2.3.0, thats why console is trying to create 1.3 version scripts for e.g. app/config folder instead app/Config (2.0 convention).
Why this is happening, Am I missing something?
If you were using v1.3.2 before downloading 2.3.0 version then it is possible that you might have set path for v.1.3.2 in your environment settings. So you need to change that to your latest version.