Parse error when parsing manifest. Discontinuing installation - android

I have an apk that installs fine on all my devices except on an old Samsung Galaxy J5 (and on a Huawei Y3).
I had copy the APK on the device via USB and try to install it with the "my files" app. The log is as follows:
02-08 11:36:56.226 1647-1674/? D/ActivityManager: Launching com.google.android.packageinstaller, updated priority
02-08 11:36:56.226 1647-1647/? D/GameManagerService: NotifyRunnable. pkg: com.google.android.packageinstaller, type: 4, isMinimized: false, isTunableApp: false
02-08 11:36:56.226 1647-1647/? D/GameManagerService: unexpected mPrevNotiType: -1
02-08 11:36:56.246 1647-1836/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:843 com.android.server.policy.PhoneWindowManager.notifyToSSRM:9071 com.android.server.policy.PhoneWindowManager.access$2100:330 com.android.server.policy.PhoneWindowManager$PolicyHandler.handleMessage:1268 android.os.Handler.dispatchMessage:102
02-08 11:36:56.246 19954-19954/? W/PackageInstaller: Parse error when parsing manifest. Discontinuing installation
Did anybody come across something like that as well?
I´ve checked the option that I can install APK from unknown sources so that can´t be the problem. And I´ve tried to install it from SD-card or internal memory with no success.

If somebody comes around the same problem. I was able to fix it by not using the signing function in Androidstudio but by manually using jarsigner and zipalign from java and the android-sdk-tools.

Related

Android studio throwing error Invalid packageName while trying to run the app

I am having one android project with diffrent build flavours like "Debug,release,SIT,UAT,...".Based on the build variant the package name is changing(Dynamic).Like if i select SIT the package name would be com.abc.xyz.SIT and if i will select UAT it will be like com.abc.xyz.UAT.(Suffix).
This is working very fine previously,Suddenly it stopped working with an error as below
2022-12-30 15:46:32.988 562-4108 ActivityManager system_process W Invalid packageName: com.mbb.mketrade.sit 2022-12-30 16:24:03.265 562-932 ActivityManager system_process W Invalid packageName: com.mbb.mketrade.sit
Surprisingly...I am able to generate the signed bundle and apk from the same source code from the android studio and can run the exported apk/bundle to the emulator but when i am trying to run it manually by hitting "Run" option it always give me error "INVALID PACKAGE NAME".
I have tried couple of steps as google suggested as below without luck.
1)Checked my manifest and build.gradle file where i have. not changed anything.
2)Tried creating a new emulator
3)tried invalidating caches and restarted the emulator.
I am still looking for any solution.Can anyone please help me on this.
I have attached my run configurations.
Run Configuration
Thank you everyone.

INSTALL_FAILED_MISSING_SHARED_LIBRARY error in Android Studio - Java/Kotlin and Visual Studio - Xamarin

I am wanting to debug and install my application on a physical clock.
First I tried to create the application in Xamarin.Android, I finished the application and it worked very well in an emulator, but when I tried to send to the device, the following error appeared:
ADB0010: Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY: Package couldn't be >installed in /data/app/AppXamarinWear.AppXamarinWear-1: Package >AppXamarinWear.AppXamarinWear requires unavailable shared library >com.google.android.wearable; failing!]
em Mono.AndroidTools.Internal.AdbOutputParsing.CheckInstallSuccess(String >output, String packageName) na >E:\A_work\1824\s\External\androidtools\Mono.AndroidTools\Internal\AdbOutputP>arsing.cs:linha 341
em Mono.AndroidTools.AndroidDevice.<>c__DisplayClass95_0.>>b__0(Task1 t) na >E:\A\_work\1824\s\External\androidtools\Mono.AndroidTools\AndroidDevice.cs:li>nha 753
em System.Threading.Tasks.ContinuationTaskFromResultTask1.InnerInvoke()
em System.Threading.Tasks.Task.Execute() 0
Then I created an empty project in AndroidStudio, just created the project, did not change any line of code, and tried to run the application on the device, so I got the following error:
Installation failed with message Failed to commit install session 1131471407 >with command cmd package install-commit 1131471407. Error: >INSTALL_FAILED_MISSING_SHARED_LIBRARY: Package couldn't be installed in >/data/app/br.pinheiros.weardebug7-1: Package br.pinheiros.weardebug7 requires >unavailable shared library com.google.android.wearable; failing!.
It is possible that this issue is resolved by uninstalling an existing >version of the apk if it is present, and then re-installing.
I understood that the two solutions are bringing the same error, something with Google Api, I have already changed all the developer settings in Wear.
Model: Zeblaze Thor 4 Pro

React-native-webview: net::ERR_FAILED

Bug description:
The first time I open my app the website loads correctly in the WebView. Then I go to the homescreen and after a while I return to the app and gets the following error:
Website not available
The website at https://www.example.com?param=value could not be loaded because:
net::ERR_FAILED
Has anyone seen this error before?
Here is some logs from Android Studio that may or my not be related/useful.
2019-06-24 10:59:11.233 16101-16166/? W/cr_ChildProcLH: Create a new ChildConnectionAllocator with package name = com.android.chrome, sandboxed = true
2019-06-24 10:59:11.237 16101-16101/? I/cr_BrowserStartup: Initializing chromium process, singleProcess=false
2019-06-24 10:59:11.239 16101-16101/? W/ResourceType: Failure getting entry for 0x7f130537 (t=18 e=1335) (error -2147483647)
2019-06-24 10:59:11.241 16169-16169/? E//system/bin/webview_zygote32: failed to make and chown /acct/uid_99051: Permission denied
2019-06-24 10:59:11.241 16169-16169/? E/Zygote: createProcessGroup(99051, 0) failed: Permission denied
2019-06-24 10:59:11.244 16169-16169/? W//system/bin/webview_zygote32: Using default instruction set features for ARM CPU variant (cortex-a9) using conservative defaults
2019-06-24 10:59:11.248 1700-6616/? I/ActivityManager: Start proc 16169:com.android.chrome:sandboxed_process0/u0i51 for webview_service dk.MYAPPNAME.app/org.chromium.content.app.SandboxedProcessService0
2019-06-24 10:59:11.264 1991-1991/? I/chatty: uid=10016(u0_a16) com.android.systemui identical 1 line
2019-06-24 10:59:11.265 16169-16169/? I/SamplingProfilerIntegration: Profiling disabled.
2019-06-24 10:59:11.289 16197-16197/? E/asset: setgid: Operation not permitted
To Reproduce:
I have only been able to reproduce this error in release - not in debug. This error happens after loading the app the first time, then leaving it and return to the app after a few hours.
Maybe it is related to cache.
The problem persist when I force quit the app. If I reinstall the app it is working for a while.
Expected behavior:
Website should fully load.
Screenshots/Videos:
Environment:
- OS: Android (Huawei P20 Pro and multiple other Android phones)
- OS version: Android 8
- react-native version: 59.3
- react-native-webview version: 5.6.2
I found a fix for this issue!
It looks like a broken service worker stalled the website.
I solved it by using the injectedJavascript prop in my WebView to inject the following lines of code:
navigator.serviceWorker.getRegistrations().then(function(registrations) {
for (let registration of registrations) {
registration.unregister();
}
});
It is a bug in Google Chrome 75.

Google Dynamic Delivery INSTALL_FAILED_INVALID_APK

I can download success and it also return installed success result.But i am getting the following error:
E/Finsky: [2] com.google.android.finsky.cq.k.onReceive(20): Error -504 while installing pkgname.pkgname.pkgname: INSTALL_FAILED_INVALID_APK: Package couldn't be installed in /data/app/pkgname.pkgname.pkgname-S4Ty06YpxYgYiWkxtqNmWw==: Package /data/app/pkgname.pkgname.pkgname-S4Ty06YpxYgYiWkxtqNmWw==/split_dynamic_name.apk code is missing
finally i fix it.
enable multiDex support

Calabash Android runtime error : Could not remove keyguard

I am getting the below error when i start the test server. The steps I followed are:
1) calabash-android resign features\com.whatsapp-v2.12.114-450480-Android-2.1.apk
2) calabash-android build features\com.whatsapp-v2.12.114-450480-Android-2.1.apk
Done signing the test server. Moved it to test_servers/55a1d403d4a789d5d979742ac47bc35c_0.5.10.apk
3)adb devices
List of devices attached
192.168.231.101:5555 device
4) calabash-android console features\com.whatsapp-v2.12.114-450480-Android-2.1.apk
5) irb(main):001:0> start_test_server_in_background
Then i see the below error..Please help
Starting calabash-android console...
Loading C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/irbrc
Running irb...
*** WARNING: You must use ANSICON 1.31 or higher (https://github.com/adoxa/ansicon/) to get coloured output on Windows
irb(main):001:0> start_test_server_in_background
Starting: Intent { act=android.intent.action.MAIN cmp=com.whatsapp.test/sh.calaba.instrumentationbackend.WakeUp }
Error type 3
Error: Activity class {com.whatsapp.test/sh.calaba.instrumentationbackend.WakeUp} does not exist.
RuntimeError: Could not remove the keyguard
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:567:in `block in wake_up'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/retriable-1.4.1/lib/retriable/retry.rb:27:in `perform'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/retriable-1.4.1/lib/retriable.rb:9:in `retriable'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:566:in `wake_up'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:590:in `start_test_server_in_background'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:133:in `start_test_server_in_background'
from (irb):1
from C:/Ruby193/bin/irb:12:in `<main>'
irb(main):002:0>
the keyguard is basically the feature that allows locking your android phone (with or without PIN). calabash has builtin code to handle unlocking on your phone in this case as long as the phone is not locked by pin\password.
check if your device is locked using pin\password and remove it

Categories

Resources