Okay, let me first apologize by saying this is my first post on stackoverflow and haven't been coding that long so this may be a simple error on my part. Also let me thank you ahead of time for trying to help me. So this is basically what is ailing me, I have a app i have coded that is used to set wallpapers on android phones and recently have been submitted to blackberry's appworld.
I have never had any issue with the app until the other day when all of a sudden when i changed the package name to a new one. Note this is of a fresh install of the app. But for some reason the Blackberry Z10 is opening the app for about a second and shows me a black screen for less then a second and then close. However, my eclipse's logcat states otherwise and that it is still loading. Note that I have other apps using the same setup and library as this app and also have recently changed their package names and haven't run into this problem. Also this only happens on Blackberry Phones and doesnt give me this issue on any normal android phones.
Here is my logcat: http://pastebin.com/EzD6eQaU
If you have any idea why this is happening please let me know.
Thank you again,
Dalton
It took a while but i found out what was my issue. Blackberry has a package name character limit of at least 50 characters long. Any more then that and your app wont work on blackberry.
Related
There seem to be too many bugs which have not been properly documented, regarding android studio. I am trying to run a basic Hello world app, and this error is truly making me give up any more efforts.
What I did:
Open Android studio(also tried running as administrator) and tried to run the default Hello world app on an Android 10 device(Xiaomi). At the start it shows Failed to start monitoring 7D8XXCOJGQQCZLJV(device number). At first I ignored it being a beginner and clicked on the run button. The file was successfully built and the RUN section shows 'Install successfully finished'.
Now for clarity here are some screenshots that will display what happened on my android device after the above steps:
The app seemed to be installed correctly, but whenever I click on the app logo the response I get is really frustrating:
As per the this link I tried to go to the device manager and do some changes, by setting and enabling Xiaomi drivers for Portable devices.
But then windows shows:
If anybody knows how to solve this, please do help me in doing so. It is quite discouraging to experience so many errors, right at the beginning. If somebody could give a working solution then that would really help me in continuing my android journey.
There was just a tiny error that led to this entire problem. This was because I had set the value of android:exported="false" in the main activity, which had to be set to true. Hope that this may help anybody in the future!
set the value of android:exported="true" in the AndroidManifest
Hey guys and girls for a the past week I've grown a lot of interest in android studio (even without knowing quite much about it) I decided to create an app that I deemed quite useful. However the app required maps to be integrated in it and I really did not know what I was doing and at one point I started messing with the settings and then all hell broke loose and I kept getting AAPT2 errors and I even tried to fix this issue with the gradle properties line that you add (I forgot the line of code to add). Anyways it still didnt work. However I rembered that I always kept the good version (before I broke everything) of the app on my phone. So when I go in my phone the app is there and it works just fine. Ive tried so many things to get the source code from the app on my phone without any succes. My question is, how can I get the source code back from the working app onto my laptop to continue coding in android studio? If it helps I am using Linux 18.04 LTS and running the newest version of android studio. Thank you for any help from you guys. This means a lot to me.
You can’t get back the ‘source code’ from an already compiled app.
You should consider using some version control platforms like git from the next time
I'm having a problem where an app I'm developing is working on mobile devices (tested on 4 different devices), but crashing when I try to test it on my tablet. The tablet I'm using is a Tesco Hudl 2, which, although being a good quality low cost device, lacks adb drivers and so you can't debug apps through USB and get the Logcat data. The app was developed using Android Studio.
With other apps I have developed, I have just set up ACRA in the project so I can still get debug information from a crash. This time however, the app is crashing without any information from ACRA and so I'm not quite sure what is going wrong. I'm pretty sure I've set up ACRA correctly given that I've used it in several projects before and see nothing wrong this time. Can it be that whatever is going wrong is happening too early for ACRA to catch?
I have pulled out all the code from the activity so the only thing that happens in code is that ACRA gets initialized in the derived Application class (note that the crash exists without ACRA). The app also uses Google maps and a provider for search suggestions. If there is any code anyone wants to see just ask, but I'm unsure what exactly to post up since everything else was stripped out. So, does anyone have any idea on what I can do to solve this, or what tools I can use to catch whatever sort of errors happen so early in the apps lifecycle?
Thanks
Update with strange behaviour... Downloaded Crashlytics and it also did not catch the crash. I copied the project and removed every .java file except the Application, Activity and provider. The provider functions were empty (save for the return value of 0/false/null/whatever), the application class just initialized Crashlyitcs and the Activity class was empty. This then worked, I was even able to add in a lot of the code and get the google map to load.
Now if I do the same in my main project, except don't delete the .java files, the crash still happens. The classes in these files are not used so I have no idea how they can be causing the crash. Otherwise all the xml, gradle, resources are identical (except the package and app name). Very confusing...
Consider using one of the apps to view logcat on the device:
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
https://play.google.com/store/apps/details?id=org.jtb.alogcat
Also try using Crashlytics. Maybe it will catch your crash?
But yeah, it's possible to have a crash before any crash reporter (ACRA or Crashlytics) will have a chance to catch it.
And one more note, maybe there is a way to enabled ADB over WiFi.
Normally you would need to enable it via adb but maybe in case of this cheap and strange tablet, there is an option for that enabled in the ROM?
Ok! So it's 1am and I decided to have one final attempt to fix, which I think I did. In my manifest, I had things like
<activity
android:name=".MyActivity"
...
for example, and while this worked fine on the mobiles, for some reason the Hudl required the complete package name, i.e. com.mypackage.MyActivity. Not sure why this is the case but it appears to have fixed the problem.
My problem is, that I can't seem to deploy my app to my phone (galaxy s4) or the emulator anymore, after adding the AndroidManifest.xml to the project.
I have been working on this app for 1 or 2 days, never had a problem testing it on my phone. I wanted to add the App Icon and change the app display name and found out that it had to be done over the AndroidManifest.xml file. So after finally finding where to add it in the QtCreator, I added an Icon and changed the name. When I click deploy, it loads and then the bar turns red, without ANY error messages or nothing. It just goes red full and then goes away. Even the warnings from build are not even showing.
I hope you guys can help me, this is my first question, so if I forgot any information or asked the question wrong, please let me know :)
You need dirqml2sdk debugger libaries (if your OS is windows). You can download it from here.
My app had been chugging along fine on the Android market until last night when it was reported a customer found an error. The customer must have downloaded the latest version of the app because he tried to use it again with the latest version and the error came back.
I looked at the stack trace of the error and found it was caused by a NullPointerException when passing information between two activities, namely with the onActivityResult() method.
I checked the code and can't find what could have caused the error. I tried to figure out what steps the user took to get the error, but found nothing wrong, on the emulator Android 1.6 /Android 2.2 and my own phone (Android 2.2). I couldn't find any problems no matte rhow much I tried to crash the system.
Another thing that is strange is that the particular onActivityResult method is called a lot in my app. So it is odd that only one user has reported problems.
Also, it says the user's platform is "OTHER". I don't know what device that could be.
So my questions are:
1) Could this problem be an issue with the user's device and not my application?
2)What to do when you cannot find the cause of a crash?
1) Yes, they may have a custom ROM; they're known for doing things like this.
2) Unless you can reproduce it, you [probably] can't fix it.
Can you contact this customer? If not, there may be nothing you can do.