Closed GoogleCodeExporter closed 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
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:
I get the same Parse Error too.
Thanks.
Original comment by sitym...@gmail.com
on 18 Feb 2015 at 9:42
Same issue with RC4
Original comment by sitym...@gmail.com
on 18 Feb 2015 at 9:47
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
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
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
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
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
Mentioned solution worked fine for me. Thank you.
Original comment by ronin...@gmail.com
on 4 Mar 2015 at 6:41
Used a different signing tool and it worked.
Original comment by ilanshul...@gmail.com
on 8 Mar 2015 at 5:39
Original issue reported on code.google.com by
ronin...@gmail.com
on 3 Feb 2015 at 2:01Attachments: