New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 872233 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Error -505

Reported by claudiae...@gmail.com, Aug 8

Issue description

CUANDO INTENTO ACTUALIZARLO ME DICE QUE NO SE PUEDE INSTALAR QUE HAY UN ERROR -505 Y YA HE INTENTADO ACTUALIZARLO 5 VECES 


 
Screenshot_2018-08-07-18-24-33.png
196 KB View Download
Cc: changwan@chromium.org cma...@chromium.org
Components: -Mobile>WebView
I saw this yesterday when I am trying to update Chrome on Android 5.1.1 too.

Play Store will show Unknown error -505 and the update failed.

I think this is a Play Store issue? Removing WebView component since I saw this for Chrome too.
A quick search in internal indicates -505 means the signing key doesn't match. I am getting this error because of I am using an old test device probably, but don't understand why external people getting this error.
Cc: satyavat...@chromium.org aluo@chromium.org amineer@chromium.org
Labels: Needs-TestConfirmation
ctzsm@, could you post the spec of the device here? Is it a userdebug build? cc'ing aluo@ and satyavathir@ for test repro.
The device I am testing is Nexus 6, userdebug 5.1.1 LMY49K.
screencap.png
410 KB View Download
I see below in the log, full log attached.

D/Finsky  ( 4314): [1] PackageInstallerImpl.cancelSession: Canceling session 199100045 for com.android.chrome
E/Finsky  ( 4314): [1] PackageInstallerImpl.handleCommitCallback: Error -505 while installing com.android.chrome: INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.android.chrome signatures do not match the previously installed version; ignoring!
logcat.txt
15.7 KB View Download
Labels: Needs-triage-Mobile
Labels: -Needs-triage-Mobile
Cc: -amineer@chromium.org
No longer on the Chrome team, e-mail me @google.com if any attention still required from me here, otherwise good luck!
Try "adb uninstall com.android.chrome" from the command line and then reapplying the update worked. This fixed it for me.

Sign in to add a comment