I would like to capture the traffic of the IONOS App (https://play.google.com/store/apps/details?id=com.oneandone.ciso.mobile.app.android&hl=de&gl=US).
The reason is simple: I need the API to configure my server and the support told me that i have to find it out by myself.
So I modified the apk and after the login it crashed, never had this behaviour before...
I tried to install the original apk file and it also crashed. (adb install <name.spk>)
(yes, i turned of signature verification for apps installed via usb.)
Any ideas how I could figure out the reason the this issue?
Other apks I could install this way without any problems.
Thanks for your help
Max
Related
I built an android application and signed the apk following all the steps on this tutorial. Even though the APK builds successfully after installing it on a mobile device it fails to load. I only get a white blank screen. I've searched for solutions and tried most of the suggestions but with no luck.
I then decided to start the project from scratch and guess what? the problem still persists. What could I have possible done wrong? I don't really know where to look because I don't even get an error message.
Please help???
I would try debugging that with a tool like GapDebug (https://www.genuitec.com/products/gapdebug/). I would:
Download and install GapDebug.
Attach your device to your PC/Mac via a USB cable.
Deploy your APK to the device and run it.
In GapDebug, choose your app as the app you want to debug.
At this point you may already see one or more errors showing up in the GapDebug console. If not,
On the device, restart the app.
Check the GapDebug console for errors.
I'm able to serve and run my app on Android (emulators, real device over ADB), but when I try to package the APk and install it on a device, I get an error. It seems like the package works just fine (an APK comes out with no error), but when I try to install my device says:
An existing package by the same name with a conflicting signature is already installed.
My sample app name is "boop" and I just made the keys/alias from scratch, so I'm not sure I really believe there is a conflict.
Anyone seen this before? Any ideas?
Doh! Figured it out.
I'd tested the application over ADB on this device. Seems like that actually installs the APK (which might be common knowledge, but I pictured some kinda temporary thing).
To get my actual signed APK to install, I just needed to uninstall the current version of "boop" on my device.
After 3 days of googling I am at my wits end witho no solution to this.
I have written a System app with System privileges (INSTALL_PACKAGE permission) on android. It is a part of a firmware being developed.
Now I want to test it on my device. I am just not able to do it. I have a rooted device with android 4.2.2.
I tried installing an it by copying it on /system/app But its not showing as installed. I am using eclipse debug keys currently. Do i need to sign it with android signature keys?
I tried doing the same with other market apps and was able to install them as System app this way but not my own app.
Pls suggest.
Thanks
I did a lot of searching, but couldn't find a solution for my problem. I have a complete Android app which runs perfectly in the emulator. The signing process works fine, but as I copy the .apk-file on my phone and try to install it, it says, that nothing was installed.
Installing the app via eclipse and a USB cable works, but I can't share the app that way.
Additionally unknown sources for apps are accepted.
Do you have any idea? I'm quite embarassed, that I have to ask this here, but I don't see another way...
If you have previously debug signed application installed. Then you need to uninstall the app first. Open terminal and type adb uninstall <your app package name>
I create an APK and install it on the device. All works OK.
Then I try and run the app from Eclipse and it gives the error above. I didn't make any changes or even need recompiling. I tried running it as debug as well as release and both have the same errors.
Something is messed up somewhere as this used to work :(
EDIT: If I want to send out a pre release to users that have a normal install from the market, does that work ok, if I just send them the APK?
This happens when you for example install or run applications with the same package but signed with two different(may be debug) keys. Just uninstall the application and run it from Eclipse againg.
You should be able to uninstall the application (either though the Android App Manager or apk uninstall <application package-path>) and then deploy it. It seems to get confused when you do a proper install then try to deploy a dev build over it.
You may have messed up your debug certificate. Try to remove it from ~/.android/debug.keystore (Linux/Mac OS X); or %USERHOME%/.android on Windows.
then uninstall using adb your app : adb uninstall yourpackagename
And try to launch it again from eclipse.
It is neither necessary nor desirable to perfom an uninstall of the application if, say, you want to preserve user data like settings.
I have had the same problem for a while, and my solution is simply exporting the app (like when publishing, with the release key) and intalling that .apk file on my phone (I attach it to an e-mail and send it to myself).
This will have the same effect as updating it normally through Google Play Store, and all previously saved data is retained.
It may not be as convenient as running it directly from Eclipse, but having to uninstall the application all the time is not such a great solution either.