I made an Android app (Java/Kotlin) and I've been testing it on different devices. When testing on a Galaxy S20 I get this error upon downloading the apk:
"Installation did not succeed.
The application could not be installed: INSTALL_PARSE_FAILED_RESOURCES_ARSC_COMPRESSED
List of apks:
'C:/Users/....'
Installation failed due to [...] -124"
I'm able to download and install the unsigned version of the app, just not the signed version.
I only have one Galaxy S20 to test, so not sure if it's the specific device.
Have not been able to replicate this problem on any other devices
The app is not coming from the Play Store, it's being directly
installed via Profile/Debug in Android Studio
Does anyone know what the problem could be? I think I narrowed it down to the signing of the app, but I'm not sure why the issue would be isolated for the Galaxy S20. Could it be that the S20 does not accept the hashing algorithm I used for the signing isn't secure enough for such a new device?
First enbale verify apps over usb and set logging level to off.
I hope this works
The problem was that I was using jarsigner to sign the app. jarsigner no longer works for SDK 30+, so this is why it wouldn't download onto the Galaxy S20. Everything worked fine once I switched to apksigner
Related
I want to track down a bug on Samsung Devices using Samsung RTL. Sadly i cant get that client to work on my System (macOS 10.13.1):
It just says Connecting...
Nothing happens from here.
Steps i did to come here:
Downloaded and installed newest JRE from Website:
https://www.java.com/inc/BrowserRedirect1.jsp
Enabled Java for Browser and Web-Start-Apps in Java Control Panel
Added https://img-developer.samsung.com to exeption list
Checked for Port 2600 using Network Utility:
https://support.apple.com/en-us/HT202790
Create Samsung Developer Account
Reserving an Device (Galaxy S6)
Download .jnlp-File and run it
Customer Support has answered to me. Seems like i have just selected a bad device. I chose another one and it worked :)
I have a very strange problem with my Android App and the Google Play Services.
With the debug Version of my App everthing works fine. And also when I started the release App over Android Studio on my real device it worked. But when I installed the App from Google PlayStore the Game Services stopped working after about 10 min. And I was not able to sign in again.
Then I uninstall the App from my device and tested it from Andoid Studio again. The first time it didn't work, but after reinstall it via Android Studio the Play Services worked again. Then I tried the App from PlayStore again, and first it worked again, but after a view minutes I had the same problems then before to sign in.
Any ideas?
I know it's an old post, but probably there are other developers facing that issue. You probably didn't set the fingerprint of your signing certificate of the app in the play store in your API console:
https://developer.android.com/games/pgs/console/setup
Remember, you need to register both, the key of your productive app and your development version. Don't confuse with the key you use for uploading. The released version of your app is not signed with that one, but rather with the certificate displayed in your play console under configure -> app-integrity -> app signing tab
I have been developing an application via Android Studio for some time and testing it on my phone (Galaxy S5 Active) using the app-debug.apk file. I would update the .apk then send it to my email.
On my phone, I would download and install the app and test it to see how it works.
Recently, however, I get an error:
Describe
There is a problem parsing the package.
Before, my phone would warn me about installing apps from unknown sources, to which I would just turn off the warning and it would install anyways. It no longer makes it to that point.
The odd thing about this is, other people are able to install the app still. My phone seems to be the only one that no longer wants anything to do with it.
I have looked into other options but none have seemed to fix my issue. I tried using AndExplorer to install it, same error. Ive uninstalled the old version. Ive even tried installing a different application that I made quickly to test.
Any thoughts on what the issue is?
I have a strange problem while developing in Android Studio on mac and i am using OnePlus one. While debugging if a call come on my mobile adb disconnect my device and don't show it again. Help me to solve this permanently.
Only solution that i have found and which works is in following step:
Restart mac
disconnect cable from mac and OnePlus One
Kill adb server
start adb server
Revoke developer certificate and turn off developers option.
restart onePlus One
Turn on OnePlusOne and connect device with mac
Open Android Studio
Enable developer option and then enable debugging option
After I follow these steps, fingerprint dialog show and once I allow that dialog, device starts to show.
This process is time consuming. I am facing this problem on mac.
Putting the phone in airplane mode seems to have temporarily fixed the issue for me. I still need to look at the logs and figure out what is wrong, but there seems to be a bug in the latest 5.x updates for the OPO.
Are you using EasyTether? If yes, you can disable it by using the following command:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If that does not work, open System Information utility and check your device manufacturer ID (Vendor ID). Copy that and paste it into your adb usb config by using
echo 0x9d17 >> ~/.android/adb_usb.ini
Then restart your macbook and mobile phone and try if it works.
There are several reasons your phone may not be getting detected properly, in my case it showed my phone in My Computers, and also asked me if I allowed my PC to debug on my phone. Yet it wasn't showing the phone in the android studio adb devices drop down menu.
All I did was, go to
Tools>Android>Enable ADB Integration
and it found my device. This is once I had installed my OPX driver that shows as a disk in My Computers and also Samsung USB driver. I'm talking about Windows here but the solution applies to Android Studio on any platform. So thought I should share.
I cannot seem to run this application which is supposedly ready to go to run on the Android Wear emulator.
Appreciate if someone can help me as to why this app does not actually get deployed to Watch emulator. I can see that the unaligned APK gets generated though.
I am following this guide:
http://toastdroid.com/2014/07/18/developing-watchfaces-for-android-wear/
Code is available at:
https://github.com/twotoasters/watchface-template
To install watchface you need to generate signed APK and push it to phone that is connected to that emulator, and install it there. After 1-2 minutes watchface should appear on the Wear device - if doesn't sync apps by companion app.
Also make sure that package for phone contains 'wear' part.
The key here is that you're using the emulator. If you run WatchfaceActivity.java from the Wear module on the emulator, you will see the watch appear on screen, but as an activity that can be dismissed.
If you then try to select it as the default watch face, you will be met with a black screen. I have only seen the emulator display the custom watch face (as a watch face, not a running activity) once and it seemed to have been a fluke.
The best way to develop custom watch faces is to run them as stand alone activities until it appears to be done, then go through the trouble of exporting a signed APK and run it on a real device connected to a real watch. At that point you can fix any small issues that remain.
please run you application on phone which has 4.3 or above platform.
install Android wear launcher apk on phone .
then connect wear emulator and phone using adb command.
adb -d forward tcp:5601 tcp:5601