SK-Yang / android-apktool

Automatically exported from code.google.com/p/android-apktool
0 stars 0 forks source link

Gmail 5.0.1 (1642443) - Parse error #755

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Decompile and recompile without any errors
2. Put that recompiled app to phone, it's show "android" icon(the default icon 
for every app), not the original. 
3. Error message - "Parse error - there was a problem parsing the package" when 
i try to install. Flashable zip doesn't work also. 

What is the expected output? What do you see instead?
expected: Decompile Successful! 

The result is same using Advanced apk tool, Tickle my android or classic cmd 
commands and latest apktool rc3.

What version of the product are you using? On what operating system?
apktool_2.0.0rc3.jar, jre 1.7.0.76, win 8.1 64 bit

Please provide any additional information below.
Phone Motorola Moto G XT1032, Android version 5.0.1
Attached decompile/recompile logs.

Original issue reported on code.google.com by ronin...@gmail.com on 3 Feb 2015 at 2:01

Attachments:

GoogleCodeExporter commented 9 years ago
Do you have a logcat of the install failing? (You can run `adb logcat` in a 
shell, trigger the install and wait).

This will help expose the real error. Also you could upload the version of 
Gmail you are using as that'll help me test/isolate the problem.

Original comment by connor.tumbleson on 3 Feb 2015 at 8:48

GoogleCodeExporter commented 9 years ago
Gmail apks uploaded to dropbox - 
https://www.dropbox.com/sh/cpcsrkmhg1maovm/AADcjFJT1VKlv_xCv_RX_ADpa?dl=0

Thanks in advance.

Original comment by ronin...@gmail.com on 3 Feb 2015 at 9:14

Attachments:

GoogleCodeExporter commented 9 years ago
I get the same Parse Error too.

Thanks.

Original comment by sitym...@gmail.com on 18 Feb 2015 at 9:42

GoogleCodeExporter commented 9 years ago
Same issue with RC4

Original comment by sitym...@gmail.com on 18 Feb 2015 at 9:47

GoogleCodeExporter commented 9 years ago
Well the bug still is open isn't it?

I believe this is a duplicate of 526. I have no proof of that though, once I 
double check I will either close or mark appropriately. 

Original comment by connor.tumbleson on 18 Feb 2015 at 1:16

GoogleCodeExporter commented 9 years ago
Yep. This is a duplicate of 526. Worked fine after fixing it.

AndroidManifest.xml (broken)
<provider android:authorities="@string/eml_attachment_provider" 

That is a @string reference for a provider. During rebuild this resource is 
made public to retain resource IDs. Due to a bug or something, public resources 
in the android:authorities are not allowed, otherwise will cause parse error 
and not install.

Following the reference to its literal value and replacing it like so.

AndroidManifest.xml (fixed)
<provider android:authorities="com.google.android.gm.provider.eml.attachment"

Original comment by connor.tumbleson on 3 Mar 2015 at 3:57

GoogleCodeExporter commented 9 years ago
I changed that entry and still got a parse error when trying to install

Original comment by ilanshul...@gmail.com on 3 Mar 2015 at 11:58

GoogleCodeExporter commented 9 years ago
1. Did you sign the apk?
2. ROM? Android version?

Its hard for me to do anything when I can't duplicate the problem.

Original comment by connor.tumbleson on 4 Mar 2015 at 1:49

GoogleCodeExporter commented 9 years ago
I tried it with and without signing.  Android 5.0.1 stock Samsung XXUHOA7

Original comment by ilanshul...@gmail.com on 4 Mar 2015 at 10:34

GoogleCodeExporter commented 9 years ago
Mentioned solution worked fine for me. Thank you. 

Original comment by ronin...@gmail.com on 4 Mar 2015 at 6:41

GoogleCodeExporter commented 9 years ago
Used a different signing tool and it worked.

Original comment by ilanshul...@gmail.com on 8 Mar 2015 at 5:39