"Error package file was not signed correctly" updating via GoogleStore

[GoogleCodeExporter]

What steps will reproduce the problem?

1.
Try to do an update version via GoogleStore (to the Aug 9, 2013 release)

2.
Observed to downloads successfully

3.
While installing, get popup dialog saying "Error package file was not signed 
correctly"

What is the expected output? What do you see instead?
Expect to see "Open MyTracks", see an error instead :-(

What version of MyTracks are you using? 
current version I have is 2.0.4, works well.

On what version of Android? 
2.2.2

On what phone?
Samsung GT-I5510M

If possible please provide a log by uploading here.
Exception here
08-16 16:01:25.133 W/PackageParser(  163): Exception reading 
res/color/common_signin_btn_text_dark.xml in /mnt/asec/smdl2tmp1/pkg.apk
...
08-16 16:01:25.133 E/PackageParser(  163): Package 
com.google.android.maps.mytracks has no certificates at entry 
res/color/common_signin_btn_text_dark.xml; ignoring!
08-16 16:01:25.133 I/PackageHelper(  163): Forcibly destroying container 
smdl2tmp1

Please provide any additional information here:
I have seen others mentioning what seems to be the same fault on the 
GoogleStore review, though also I see others install successfully - must be a 
dependency on the phone or older android version so not everyone affected?

I tried a couple of times every day since release, on two unrelated networks 
(WiFi, never over phone data). Other applications have benn installing fine. 
Currently about 30MB free in phone storage.

<an awesome app, BTW!>

Trevor

Original issue reported on code.google.com by twelling...@gmail.com on 16 Aug 2013 at 10:20

Attachments:

• log.txt

[GoogleCodeExporter]

I also tried a manual install of MyTracks-2.0.5.rc4.apk using EasyInstaller - 
EasyInstaller reports "Package not installed" and log has the same exception : 
 W/PackageParser(  163): Exception reading res/color/common_signin_btn_text_dark.xml in /mnt/asec/smdl2tmp1/pkg.apk as above

Original comment by twelling...@gmail.com on 19 Aug 2013 at 3:03

[GoogleCodeExporter]

I have been seeing the same behavior ("Error package file was not signed 
correctly") the last couple of days, too. 

Version of Android is 2.2.2.
Device is an Motorola MB525 (Defy)

Original comment by stefan.h...@gmail.com on 27 Aug 2013 at 10:12

[GoogleCodeExporter]

Same issue Samsung GT-I5500 android 2.2

Original comment by jackiede...@gmail.com on 27 Aug 2013 at 4:56

[GoogleCodeExporter]

LG Optimus (VM670), running 2.2.1

I am low on space, and one or more recent updates may have run out of room 
while updating, if that helps. I've cleared out a lot of space (~30M available 
on the internal storage) and uninstalled My Tracks completely.

Still no joy (as above) when installing fresh.

Original comment by maurizio...@gmail.com on 28 Aug 2013 at 7:53

[GoogleCodeExporter]

I've tried to installed since yesterday, but it shows same message; also tried 
to instal manually, same.thing.
HTC Desire HD w/Android 2.2.1

Original comment by javier.a...@gmail.com on 29 Aug 2013 at 1:13

[GoogleCodeExporter]

Add me to the list of those having problems.

Original comment by jcon...@gmail.com on 1 Sep 2013 at 10:42

[GoogleCodeExporter]

Me too! Been this way for a week (now Sept. 2). Motorola Blur running Froyo 
2.2.1.

Original comment by westcarl...@gmail.com on 2 Sep 2013 at 8:17

[GoogleCodeExporter]

Yeah i removed it to see if i can reinstall it and now its gone.  Hope they
email us when fixed
  Luv the app.

Original comment by jcon...@gmail.com on 3 Sep 2013 at 4:23

[GoogleCodeExporter]

Those that have deleted the app can download the APK from Google. Just search 
"code.google.com my tracks", under the downloads on the left do show all, and 
find the previous version. Then, just get it to your device. I like AirDroid.

Looks like all of those of us who are having problems (that have included their 
version numbers) are in the 2.2.x range. Wonder if that helps the code gurus.

Original comment by maurizio...@gmail.com on 3 Sep 2013 at 6:16

[GoogleCodeExporter]

I too removed and reinstalled the package only to get the same error message. 

Original comment by kmacd...@gmail.com on 5 Sep 2013 at 7:25

[GoogleCodeExporter]

Fix please love this app.

not signed correctly" updating via GoogleStore

message.

Original comment by jcon...@gmail.com on 6 Sep 2013 at 1:38

[GoogleCodeExporter]

Same issue.  Phone LG Optimus P-999 and Android 2.2.2.

Original comment by deb...@brentnell.ca on 9 Sep 2013 at 1:40

[GoogleCodeExporter]

Motorola Defy, Android 2.2.2. Same problem. cannot install from market. 
Downloaded apk, still cannot install with the same error (package not signed 
correctly). 
If this is the way google forces people to later Androids, then it's very bad 
way. 

Original comment by pypetuk...@gmail.com on 17 Sep 2013 at 11:20

[GoogleCodeExporter]

pypetuk, you can download the not-quite latest apk and get back to where you 
were.

But I'm with you wrt the not so subtle approach to upgrading. If it were simply 
the app required newer features, there's a real way to deal with that. This 
seems to be some sort of bug in the signing/certificate process, and they don't 
seem real excited about resolving it, given how long they've let this go.

About what I expected but less than I hoped for.

Original comment by maurizio...@gmail.com on 17 Sep 2013 at 2:42

[GoogleCodeExporter]

I have more or less the exact same problem. Some time ago when running an 
upgrade in went wrong. From now on it gets an error as stated in this thread. 
My unit is an Motorola Defy with 2.2.2

It worked for me when installing version 2.0.4.rc3.apk

Original comment by wiss...@gmail.com on 19 Sep 2013 at 11:18

[GoogleCodeExporter]

So, when is google going to address this or are they just going to let everyone 
wonder what's going on?  Its been going on for a good 2 months.  I know when I 
have a small issue like this my users don't want to wait 2 months without any 
word.

Original comment by kpois...@gmail.com on 30 Sep 2013 at 11:42

[GoogleCodeExporter]

Same.  On 2.2 HTC Desire. Very surprised how long this is going on. Don't need 
the latest version. But surprised by the lack of interest from Google. 

Original comment by rupert.b...@gmail.com on 6 Oct 2013 at 8:00

[GoogleCodeExporter]

Same issue. HTC Desire, Android 2.2.2
Error message: "Error !!
package file was not signed correctly !"

Original comment by geofr...@gmail.com on 14 Oct 2013 at 1:48

[GoogleCodeExporter]

The problem was gone after switching from Android 2.2.2 to 2.3.3 (HTC Desire)

Original comment by byc...@gmail.com on 15 Oct 2013 at 5:38

[GoogleCodeExporter]

How do i know what version i have and or how do i upgrade?

Original comment by jcon...@gmail.com on 15 Oct 2013 at 8:59

[GoogleCodeExporter]

Is it possible that this is related to the issue of signing packages with JDK7 
vs JDK6 ? This was reported to have a similar effect (package looks fine but 
some users cannot install it), see 
http://blogs.kiyut.com/tonny/2012/06/07/how-to-build-and-sign-android-apk-using-
jdk-7-with-netbeans ...

If you encounter this problem, remember to "vote" for this issue (click on the 
star next to the issue title on the top of this page) to get this up the charts 
(and hopefully make it visible enough to attract developer attention) ?

Original comment by cere...@gmail.com on 16 Oct 2013 at 5:41

[GoogleCodeExporter]

Here's another "Me too" type post.  Same issue "Package file was not signed 
correctly".

Phone info:
Samsung Galaxy S (1) [SGH-T959 "T-Mobile Vibrant"]
Firmware version 2.2
Kernel 2.6.32.9
Build FROYO.UVKB5

Rolling back to the previous version (2.0.4.rc3) works fine.

Original comment by millma...@gmail.com on 28 Oct 2013 at 11:40

[GoogleCodeExporter]

Same result.
package not signed correctly.

Lg optimus One
ver 2.2.2

Original comment by matteo.s...@gmail.com on 29 Oct 2013 at 6:22

[GoogleCodeExporter]

Me too

Samsung infuse.
This has been a problem for several months. 

Original comment by RFKel...@gmail.com on 30 Oct 2013 at 5:04

[GoogleCodeExporter]

I am also experiencing this problem. Really wanted to use this app. When will 
come the solution?

My phone is a Samsung GT-I9000B with Android. But when I install the My Tracks 
app it downloads the application but during installation it gives error: 
package file was not signed correctly. I've tried several times but can not 
install. Can you help me?

Original comment by k...@garcia.art.br on 30 Oct 2013 at 7:57

[GoogleCodeExporter]

REMOVE ME

Original comment by sandov1...@gmail.com on 30 Oct 2013 at 8:11

[GoogleCodeExporter]

Same result.
package not signed correctly.

Samsung I5500.

Android 2.2.

Original comment by dexter2...@gmail.com on 2 Nov 2013 at 7:12

[GoogleCodeExporter]

Is this abandonware? I think all it needs is a rebuild with a correct signature.

Original comment by markll...@gmail.com on 25 Nov 2013 at 5:35

[GoogleCodeExporter]

As this is licensed under the Apache Software License, we are allowed to 
download and recompile the code. With enough changes to prevent confusion, one 
could possibly even publish a modified version in the Play Store and update it 
as this project is updated.

Original comment by jos...@stevedwire.com on 25 Nov 2013 at 5:39

[GoogleCodeExporter]

Yeah, I could rebuild it.  I'm just wondering if there's anyone actively
developing or maintaining it anymore.

Original comment by markll...@gmail.com on 25 Nov 2013 at 5:59

[GoogleCodeExporter]

I'll remind folks of my earlier post: You can find the previous version of this 
app at Google. It runs fine on my 2.2 version of Android. You just need to find 
a way to download it to your phone. I like AirDroid. Then, don't update Tracks!

My understanding is this is one of those Google employee projects. Some 
employee took that free % of his/her time and wrote this. Apparently even 
maintained it. I think "abandonware" is a bit harsh for the free gift this is 
(and you can still use, just not the current version).

Original comment by maurizio...@gmail.com on 25 Nov 2013 at 6:59

[GoogleCodeExporter]

Ahh of course abandonware could also be the lucky penny you find on the
street on a bad day to pick you up. :-)

Original comment by markll...@gmail.com on 25 Nov 2013 at 7:18

[GoogleCodeExporter]

Lg p500 UK orange version
2.2
Same issue 

Original comment by bhavsa...@gmail.com on 4 Dec 2013 at 10:29

[GoogleCodeExporter]

This will be fixed in the next release.

Original comment by jshih@google.com on 13 Dec 2013 at 1:11

• Changed state: Fixed