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
I am using Google sign-in for my app, and it does get called, but when it pops up, instead of asking which account I want to use, it says "This app requires the latest version of the Google play games app". And I am sure, that Google play games app is installed because I entered my account data into there.
Edit:
I am using API version 24 on my AVD
You should check if your google play services version is 10.2.6.
Else you will have to update it.
Else specify a lower version like com.google.android.gms:play-services-games:9.8.0 in your gradle file and run.
I migrated from Eclipse to Android Studio when version 1.0 came out.
This automatically changed the google play services integration (which i use for admob and analytics) to an entry in the app gradle build file.
All my apps that use the play services now periodically crash. Apps that don't use it are working like before.
The crashing apps start up once normally. But when you close them (via recenty opened apps) and then reopen them at a later point, the screen turns black and the app will not respond.
Any idea what causes this?
The problem I'm trying to solve- I'm trying to get deep linking working, and testing it with Emulator. When clicking on posts, the links direct to the mobile web site. This is in the case of the user having permissions for the app, and the app is installed (on the emulator). In the Facebook app, it even acknowledges its out of date, but an upgrade (in app) crashes.
I also noticed that the Facebook app installed on the emulator is out of date (I installed it via adb install facebook.apk from github sdk).
SSO is working fine, and I have setup deeplinking effectively with iOS before (So I know how ti's supposed to work/test it, etc.). But the port to Android is being held back by this out of date 3rd party Facebook app. I'm assuming testing on device will solve it, because there the Facebook app will be the latest (which brings to mind- what if people haven't updated their android facebook app?).
My app settings:
I'd post code, but this seems to be pure integration and configuration issues.
Note: my app isn't published on Google Play, could that be the issue?
Also: maybe this is only testable on the device? My device is "in the mail" so trying to get this done with emulator as much as i can.
Update: Facebook told me that this requires the Facebook app 1.9.* which is not in the SDK. So, I got my hands on a device, and while I haven't solved it, at least the app bookmark functionality is working. Will update if/when I find the answer.
Update 11am: I finally got it to work!
I had to publish my app in the Play/Market.
Each time I tested, log out of FB-Android app, clear cache, and force stop. Acc.
to the documentation the bookmarks are cached. I also think the
facebook app-syncing occurs on launch, and never again. So if you
change anything in FB's app settings, you need to log out/clear
cache/stop for it to take in the fb android app.
Only one key worked, even though it says "hash" in the fb app settings, I think
my dev key was screwing things up. Double-confirm that your release
key is the same as the one listed in app settings.
The final secret sauce for me, was to turn off SSO and deeplinking, re-test
without anything set. Also, remove dev package from phone and
download from Play. (see: key mixups). then, I stepped back through
the configurations by first turning on SSO, testing, then turning on
the native deep linking.
Only works on real device, not emulator (unless you can get 1.9 installed on emulator, may work, did not go down that route to test)
Not sure if this matters, but it may: install app from Store/Play, not from Eclipse. Could be the key syncing thing.
I figured it out- involved doing the following:
I had to publish my app in the Play/Market.
Each time I tested, log out of FB-Android app, clear cache, and force stop. Acc. to the documentation the bookmarks are cached. I also think the facebook app-syncing occurs on launch, and never again. So if you change anything in FB's app settings, you need to log out/clear cache/stop for it to take in the fb android app.
Only one key worked, even though it says "hash" in the fb app settings, I think my dev key was screwing things up. Double-confirm that your release key is the same as the one listed in app settings.
The final secret sauce for me, was to turn off SSO and deeplinking, re-test without anything set. Also, remove dev package from phone and download from Play. (see: key mixups). then, I stepped back through the configurations by first turning on SSO, testing, then turning on the native deep linking.
Only works on real device, not emulator (unless you can get 1.9 installed on emulator, may work, did not go down that route to test)
Not sure if this matters, but it may: install app from Store/Play, not from Eclipse. Could be the key syncing thing.
Have you had a look at the troubleshooting tips for deep linking? (Sorry, have to ask.)
I'm wondering if perhaps the FB app on your device was not properly quit after the relevant setting changes.
I'm currently only using the Honeycomb emulator to test a new Fragment-based release, which requires the LVL licensing service. However, every time I start my app on the emulator, it fails the licensing test and my emulator cannot add Google accounts, so I can't try that way either.
How can I get it to work?
I believe that nobody has been able to get the LVL libraries working on any emulator except 2.2. See this posting and this issue report.
I am having the same issues with LVL... however to create the google account on your emulator make sure you create it with the google libraries.. IF you create the emulator with the google libraries you will get the google account set up when you create accounts.