I have an ionic app and built the android release, then did all the key and zip align steps.
Then ran this ~/Library/Android/sdk/platform-tools/adb install (the path on my computer to the apk) (apk name).apk
to test the apk directly on my phone.
I test this on my phone for hours and then go to upload this apk to the google play console and in the android folder the "build" folder that holds my apk completely disappeared. I searched my computer, trash, external hard drive, enabled hidden files, etc. but to no avail.
This build caused me problems building and I don't want to go back and spend many more hours testing so if you have any idea what might have happened or how I can retrieve the build and apk would be much appreciated!
Have you followed the Android Publishing steps here?
When this steps ended, you have example.apk. And you upload this apk with drag drop in google play console version management.
Related
I'm using Visual Studio mac for developing Xamarin, recently I released my Android app but a rare behave happened! Releasing app popped out 2 files named app.apk and app-Signed.apk and I think the 2nd one should be the one I should upload to Google Play store (am I right?), but after opening it on my device I found out many changes that was appearing in debug app are not exist in Singned one! while app.apk is OK with changes I applied to app.
Is app.apk in debug mode?
What should be app-Signed.apk and why it has this problem and how can I fix it (if answer to #1 is true)?
Sometimes Visual Studio Mac for some reason does that. Remove obj and bin folder from a project directory, and then build again. If that happens again (2 files) the odd thing that you need to upload to google play non signed one.
My application's debug apk(one in bin folder) size is 25.8 MB, I'm not using proGaurd as of now, I have multiple libraries such as Facebook, Twitter, Google play services, Vuforia, and few other graphics related jars. So my problem is when I'm generating release version apk using export wizard I'm not getting correct apk file size. Everytime I generate apk for release version the size is different( like 19MB, 21MB, 23MB ,22MB,25MB). When I install this apk on device it is crashing. I have 8GB of RAM, I cleaned project before starting process, closed all running applications except eclipse , I also run CC cleaner and started eclipse from cmd prompt with 'eclipse-clean' command but still I wasn't successful to generate correct apk.
Any suggestions to solve my problems will be appreciated.
Basically:
For a few days we are trying to download an expansion file for our apk.
But it keeps saying "Download failed because the resources could not be found."
While debugging, we found that the responseCode in LicenseValidator.verify is ERROR_NOT_MARKET_MANAGED.
Is there anyone having the same problems?
Steps taken so far:
App added to Google Play's developer account in "draft". Also added 1 Expansion file.
Uploaded a couple of days ago.
Saved, not published.
main.1.our.package.name.obb created with Zip. Files are not compressed, just stored.
Also created obb file by using JOBB.
AndroidManifest.xml: versionCode=1, added all permissions from guide.
Copied license code from console to Service script (provided by android SDK)
fileSize is set in bytes (336467473L) appr. 328 MB.
Google play accounts on test devices are set to correct developer account.
Enough free space on devices. Restart hardware and software many times.
Time of devices are not in the future.
Cleared cache and local files of Google play App and Installed app.
Several ways of running and installing the apk file by:
Running apk directly from Eclipse.
Export and sign apk in Eclipse and install it manually on devices.
Use adb to install apk on device (signed and unsigned apk)
Signing is done by keytool.
Used zipalign to align the apk file.
Test devices are Galaxy Tab 10.1 (4.0.4), Galaxy Tabpro 10.1 (4.4.2)
Allow installation of apps from unknown sources is checked on device
Problem is fixt! After publishing an alpha release in Google play's developer console and waiting a few ours the download started...
I am starting to explore the game development using unity 3d for android. I have downloaded the trial version of unity 3.3. I went through few tutorials.
I have one question that is not answered. In the normal apps which we develop using eclipse, we can deploy onto mobile by copying the apk file. What about unity 3d? How do I get the game onto my phone. I don't want to publish on market.
It is possible to transfer your assets to Eclipse. When it's integrated you can debug via your android phone. Be sure to read the tutorial on Unity's homepage. There is a step by step start-up guide and some more. Following links are worth looking at:
Getting started with Unity and Android
Official - Integrating Unity with Eclipse
Alternative link - Integrating Unity with Eclipse
It would seem that the official "integration" link is broken so I updated with a forum post that covers the same topic. However I recommend to try with the official link first.
Yes, you can simply copy the apk to your device and install it. Unity builds an apk file (and will optionally sign it using a keystore that you provide or let it generate for you). Once it has built that apk you can deploy it normally. You can even have it include a customized manifest in the apk that it builds if you want to (but it generates a nice one from your settings in the unity project by default).
There are two methods for this, as far i understand,
Using Build Settings--> Build, It builds the apk file that can be installed on your device using adb install <apk file path and name>
Using Build Settigs--> Build and Run. Which automatically installs the apk built apk file on your device if connected
go to file
-build
-select android platform(your pc has to have android development kit)
-save your apk
As it is still unanswered I try to close this question
First of all, current version of Unity 5.2 is much more powerfull than version 3.3. mentioned in original question.
What about unity 3d? How do I get the game onto my phone. I don't want to publish on market.
The same way. Unity allows you to publish build as *.apk on ocal machine and then you can just copy it to your phone and install it.
What is more cool, now you can debug your application running on phone. You have to install Unity Remote to the phone and run. Now you can set breakpoints and debug as normally.
If you change your mind and go to publish on Market - Unity will sign your *.apk
Hope this helps someone, good luck!
The Same way you generate the apk through Eclipse like that in unity you need to build the project. For that android sdk and jdk should be installed in your system and u need to show those path in the unity Preferences then u need a google keystore and need to sign in with that key store in the Publisher settings and then u are able to build the apk which will be store in your local system and you can copy that to your mobile and install the apk file.
I am trying to distribute my application to some people for testing.
I have installed it on my Desire directly from eclipse and it works fine.
To create an APK-file, I choose "Export Unsigned Application Package" directly from eclipse, and then an APK file was created. I emailed it to myself and downloaded the file to the SD-card. But when I try to install it (using ES File Browser), I get a message saying "Application not installed".
(I have already checked the "Allow installation of non-Market application" on my phone)
Any ideas?
Yeah I found the problem, see my answer below:
I did not know that even with the "Allow Installation of non-Marked application", I still needed to sign the application.
I self-signed my application, following this link self-sign and release application, It only took 5 minutes, then I emailed the signed-APK file to myself and downloaded it to SD-card and then installed it without any problem.
I did not know that even with the "Allow Installation of non-Marked application", I still needed to sign the application.
I self-signed my application, following this link self-sign and release application, It only took 5 minutes, then I emailed the signed-APK file to myself and downloaded it to SD-card and then installed it without any problem.
You cannot install an unsigned application on a phone. You can only use it to test with an emulator. If you still want to go ahead, you can try self-signing the application.
Also, since you are installing the application from an SD card, I hope you have the necessary permissions set. Do go through stackoverflow.com and look at questions regarding installation of applications from an SD card - there have been many and they have been asked before.
Hope that helps.
You can test the unsigned-apk only on Emulator. And as its step of application deployment and distribution, you should read this article atleast once, i suggest: http://developer.android.com/guide/publishing/app-signing.html.
For your question, you can find the below line in above article:
All applications must be signed. The system will not install an application that is not signed.
so you have to have signed-apk before the distribution of your application.
To generate Signed-apk of your application, there is a simple wizard procedure, click on File -> Export -> Android -> Export Android application.
Just follow these steps to transfer the apk onto the real device(with debugger key) and which is just for testing purpose. (Note: For proper distribution to the market you may need to sign your app with your keys and follow all the steps.)
Install your app onto the emulator.
Once it is installed goto DDMS, select the current running app under the devices window. This will then show all the files related to it under the file explorer.
Under file explorer go to data->app and select your APK (which is the package name of the app).
Select it and click on 'Pull a file from the device' button (the one with the save symbol).
This copies the APK to your system. From there you can copy the file to your real device, install and test it.
Good luck !
I cannot install an apk build with "Export Unsigned Application Package" Android SDK feature, but i can install an apk browsing the bin directory of my project after the project buid. I put this apk on my sd on my HTC Wildfire phone, select it and the application install correctly.
You need to allow your phone to install unsigned apk.
Good Luck.
You could also send your testers the apk that is signed with your debug key. You can find that in the bin folder of your project after building in debug mode.
An unsigned application cannot be installed. When we run directly from eclipse, that apk is signed with debugger key and can be found in bin\ folder of the project. You can use that for test purpose distribution also.