I know this is Unity3D question and there are more specific stack/forum sites...
Pls see attached logcat log, is there anything which gives us any clue?
Unity Splash screen appears on device, but after a few seconds it crashes. This app was OK yesterday, I added some C# code textures etc. I carefully examined the debug build logcat log. My code has not even a chance to run, the crash happens before...
Note: No Mono runtime exception in logcat log.
It works fine in Unity editor, or windows standalone build.
Again: It worked fine, with the same settings yesterday. More: The yesterday's backup sill working today, rebuild, deploy to the same device. This today's version (I1ve added textures, code etc) which is not working on the device.
See the log attached.
Don't know where to search toward... :-(
Thx for help
Download logcat log file
Related
I am very new to Kotlin and Android studio. I tried running my App through the emulator, I built in AVD manager.
Whenever I run my App it goes to the home screen, I don't know what you'll need to solve this or what causes it:
But based on what I've seen as I researched this issue, here are some info I think you might need;
-I've turned off detect adb location and set the directory to C:\Users\user\AppData\Local\Android\Sdk\platform-tools
-minimumSdk 21
-targetSdk 31
-My Api level is 25
Please whatever info you need to help me rectify this issue just ask me..
I am open to any suggestions, Thank you in advance for your help!
here's a screenshot of build error:
I'm adding a logcat error message screenshot, though they are much of error I just screen the ones that could be taken on a single shot, I hope it enough.
(Please note that previously my logcat was empty even when I was experiencing the same problem, so I created another emulator, and the logcat is no longer empty..)
You can check out the logcat to be able to see what went wrong.
I am currently working on an android project. But now when I open the emulator it shows too many errors in logcat and those are looping on it. But the emulator worked fine yesterday. Today I just wipe data in the emulator and those errors start to showing in logcat after that. I delete the emulator and recreate it but those errors are still coming. Do you guys have any idea why those errors come and how to fix those?
Few images of errors that looping on logcat
image 1
image 2
image 3
image 4
The emulator that I am using
image 5
Some errors in AS are fatal, it means that your app or AVD can't run with them. But some of them are not important issues, you can run your app or AVD even there are red lines in logcat.
Utter Wits end. Tried all solutions: clean build, sync project files with gradle, build Bundles, Build APKs, disable and re-enable instant runs etc.
Followed Exact steps outlined in other threads/ posts but still couldn't get the app to run on my physical Samsung Galaxy S7 phone. It was working fine previously, but now couldn't get it to work. App still able to open on Emulators though.
Needed to test out gyroscope and accelerometer sensors on a physical phone which emulators can't achieve as intent.
Would like to seek help from the community regarding this matter. Any idea where it has gone wrong? I have already updated my compilesdkverison and targetsdkversion in the module:app build.gradle scripts. Tried almost everything that I can think of but to no avail. Hoping to see the light and receive enlightenment from the community as I'm a novice in Android Studio.
PS: By the way, how do people add actual iamges to the post, itseems like the only way i can show an image is in the form of a hyperlink away from current page. Is there a way to just put the image directly in the post here?
Looks like there is not enough space on your phone. Try making some space on your internal memory.
Users comment on google play that app is not opening on nexus 7. I am waiting for my nexus to test that issue. Right now I do not have that device.
My app is OpenGL ES 2.0 game.
Some ppl comment on google play that app is not openning. But I do not get exception error in Crashes and ANRs in Google Play.
What could be a reason for that?
I have a lot of native code. Do native code exceptions are reported somehow?
Could it be a ConfigChooser.chooseConfig bug? Is that recommended ConfigChooser.chooseConfig for Nexus or most apps?
I can confirm that the game crashes the moment you open it on the Nexus 7, however I know why you have nothing in Crashes & ANR... no Force Close dialogue box opens at all, you get a black screen, then the game immediately quits.
I do however have the stacktrace from logcat available, the error is in some C/C++ code you have via the NDK. I have uploaded the entire log from when you open the app onto pastebin for you.
Logcat: http://pastebin.com/dq0kRxnn (the link will expire after 1 month)
I have recently completed development on a game for Android smartphones.
It was designed using the android 2.1 sdk and runs no problem on my test devices a 2.1 samsung galaxy europa and a 2.2 samsung galaxy tab and seems to run fine in the emulator for 2.3.3.
Up until recently it ran fine on my friends HTC desire S but suddenly it stopped working, crashing on start.
It would appear that the error is caused by a resource not being found.
This code has not been touched for the past 2 months and ran no problem on my 2.1 and 2.2 devices but I must have done something. It seems that suddenly that some phones can't see the resources but unfortunately I cannot replicate this bug and my friend is not around enough and is getting quite pissed at me for pestering him for me to take his phone and keep trying to fix it.
Any help would be much appreciated as this is driving me mad especially as I cannot replicate this bug with any of my equipment. I haven't even got a confirmation that it works on 2.3.3 as the people who have downloaded my app aren't leaving any useful feedback or submitting many error reports. Hopefully it is just a bug with HTC's variant of android.
I sometimes have errors like this when I'm rapidly iterating (tweak/test) on the emulator. They're usually solved by doing an "ant clean" and then recompiling. You could try cleaning and then doing a fresh build, installing it on your friends device, and then seeing if you still get the error.
-Kurtis
Have you considered/researched whether or not this actually is a resource problem...meaning does this resource actually exist in the folder Android is trying to draw from?
I'm currently facing the crash in a production application and have found the problem. This crash is only happening on HTC devices. Seems like HTC changed the core Android method that decode a Resource.
The documentation of BitmapFactory.decodeResource says :
Returns
The decoded bitmap, or null if the image could not be decode.
But HTC version of that crashes :(
In my case, I had mis-placed the "xml" folder. It was on the root of the project, but just moved within "/res" folder and the error was gone.