When I run my game through Unity Remote 5 it works well, but when I build the apk and try to install it on my device, it shows app is incompatible, I have tried changing many settings in player settings section but nothing worked for me. What can be done with this problem?
I am using unity 2017.3, the Android version on phone is 7.0 (Nougat) (I also tried on oreo but didn't work either), minsdk version in player settings is set on the marshmallow and target SDK version is on highest installed.
I have had this problem before. Maybe you can try removing the app you just have installed and trying to install the new version.
But you should complete your question with more information as someone comented.
Hope it works!
Related
I am trying to build my first android game but I keep seeing this and getting a warning.
An Image of the warnings in my preferances in unity
I reinstalled the recent version of unity and also tried manually installing them. I have selected the android versions of 9 and above.
I'm using Unreal 4.26.0 and I finally got it to launch to my Oculus Quest 2. However, it doesn't always launch the latest version.
So, I might make a change, build the project, then launch the app on the Quest via Launch => Quest 2.
Eventually, it starts running on the headset, but often it doesn't have the latest changes. If I shutdown Unreal, then restart it, it does get the latest version.
How do I consistently have it launch the latest version of the app? Is there some formula for getting it to properly copy over during launch? Thanks in advance.
I did find the solution... just in case someone else has this same problem:
I did not have all the environment variables set correctly for Android/Java. I had to make sure all these were set:
JAVA_HOME
ANDROID_HOME
ANDROID_TOOLS
ANDROID_PLATFORM_TOOLS
ANDROID_NDK_HOME
So, after making sure each of those were specified, I also had to put each into my $PATH.
I should also note that I'm using Unreal 4.26, Android SDK 10, and Android NDK 22.0.7026061. These aren't exactly what the directions call for, but the directions are a bit old. These are (mostly) the newest versions as of this writing.
I created a new empty project, switched platform to Android and started Build and Run. But when it comes to "Copying APK File to device" it just freezes and I have to restart Unity.
I installed Android SDK & NDK tools just before that (through Unity Hub). Android Build Support was installed by me manually a while ago so it was visible as installed in Add Modules window. I did not do any changes to the project. The most interesting thing is that the apk is built in my Builds folder. Not sure if it works though.
I am using Unity 2019.1.0f2. The device Android version is 9.0 (API level 28) and the minimum API set in Player is 16, so the problem should not be with API.
Does anyone know possible reasons for it?
Try to turn off the following setting on your android device.
Settings -> Developer options -> Monitor apps installed by ADB
This setting(if turned on) will ask a verrification if you want to install the app. It feels like this cuts off the connection with unity which causes it to get stuck.
Unplugging and replugging the device seems to work aswell. In case of big projects this is anoying tho since if you are to quick it will just say it lost connection and it will ask if you want to reconnect, which in turn causes the same problem.
This is the only answer that worked for me:
https://answers.unity.com/questions/1248123/build-run-apk-freezes-on-pushing-content-only-one.html
In short, Player settings -> Publishing settings -> Split application binary
First of I would ask you on what computer did you run this on? (performance wise)
Second you can just copy the .apk file to the phone and install it there. If you got to where it prompts for copying to android your apk file is fine and built.
I have a problem when i build / export my game into android's APK.
i've already replace latest tools folder to my SDK path but the problem still don't fixed.
So i tried to upgrade my Unity from 2017.2.0f3 into Unity 2018.1.0f2 and reconfigure my SDK path but still not working.
There's the error notice
Go through Unitys preferences and make sure android SDK Java SDK paths are configured. I had this error recently on a fresh install, the solution was to install https://developer.android.com/studio/releases/platform-tools ( also setting paths to platform tools in your system path can be useful while at it)
I am totally new to Cordova, but now I have installed Cordova with NPM and installed Android SDK and set up an AVD which seems to work perfectly, until I want to emulate my project. Where the actual app for some reason is not loaded into the emulator.
The following action is done:
marvin:HelloWorld$ cordova -d emulate android
cordova library for "android" already exists. No need to download. Continuing.
Wrote out Android application name to "HelloWorld"
Wrote out Android package name to "com.example.hello"
Calling plugman.prepare for platform "android"
Preparing android project...
Processing configuration changes for plugins.
Iterating over installed plugins: []
Writing out cordova_plugins.js...
Running on emulator for platform "android" via command ""/home/marvin/Development/projects/HelloWorld/platforms/android/cordova/run" --emulator" (output to follow)...
Then it start Android emulator up, but the app is not there. Does anybody have a suggestion to fix this issue, so I am capable of actually testing in my emulator?
Thank you in advance.
I just had the same problem, and I was missing PATH to platform-tools in android sdk folder, after I added it everything was in place.
I had the same problem as well; I could run the cordova emulate android command just fine, and the emulator would eventually start up and function, however, the test app was never installed on the device. I was not getting any errors from the Cordova CLI or the console or anything.
I found that there is a bug report about this issue here: https://issues.apache.org/jira/browse/CB-4285
Two solutions have been found for this issue:
1. Make sure you are using an Oracle JDK and not an IBM JDK, and
2. Make sure the AVD that emulate starts up has a min-target-sdk set to API 10 (Android 2.3.3) or higher. (This was my problem.)
Sometimes it works deleting the previously installed version of the app in the emulator. For this you could also launch it with the option "Wipe user data" checked.
Just for the record, none of the other solutions worked for me.
I had the same issue. Following solved it for me.
Make sure that API level of your AVD is greater than minSdkVersion specified in config.xml specified in your cordova app.
If anyone still having this issue:
I had a same problem with device being offline.
if ddms is running it looks after connected devices.
adb kill server
and than run ddms
Also make sure your app id doesn't begin with a number or any other character like "_". For example, if your app id is com.4company.MyApp or com._company.MyApp it just won't load on the emulator. The first one is because Java doesn't allow names beginning with a number, and the second one I guess it's a Cordova thing.
You should also use adb logcat to show the emulator errors on the command line.
For me, the app was not starting up because I had a second emulator running in the background. Uninstalling bluestacks (android emulator for windows) fixed the issue in my case. Running "adb logcat" should tell you if you have multiple emulators running.
I just had the same problem, and It was my emulator device that was with the API 15. Just updated to API 17 and the problem solved.