Bug 15502 - Package XXX has no certificates at entry XXX; ignoring!
Summary: Package XXX has no certificates at entry XXX; ignoring!
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 4.10.0.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-10-18 16:21 UTC by Jens
Modified: 2017-08-07 20:40 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
requested build.txt (337.75 KB, text/plain)
2013-10-18 16:48 UTC, Jens
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Jens 2013-10-18 16:21:40 UTC
Android doesn't like the APK files I create with "Publish Android Application" under Xamarin Studio for Mac.

when I install the APK I get the following messages:

10-18 21:46:58.061: E/PackageParser(2224): Package de.appnotize.letmetalk has no certificates at entry res/animator/fragment_left_slide_in.xml; ignoring!
10-18 21:46:58.151: D/InstallAppProgress(15200): Installation error code: -103

the installation gets canceled and the user can not install the app at all :-(

For me it looks like the "Publish Android Application" forgets to sign some files...
The Android Play Store accepts the file, so the store thinks the file is signed correctly.

The installation failed on a Nexus S, a galaxy Tab 10.1 and an Acer Iconia B1. There are reports that it works on a Nexus4, but I am not sure about it.

I will add the APK file, even if I am not sure if it helps. I have no idea what to do now :(
Comment 2 Jens 2013-10-18 16:47:46 UTC
as requested in IRC I added the following to the csproj file

  <PropertyGroup>
    <AndroidKeyStore>True</AndroidKeyStore>
    <AndroidSigningKeyStore>/Users/jens-uwe/Projects/Export/letmetalk.keystore</AndroidSigningKeyStore>
    <AndroidSigningStorePass>Ke42OgMwldsw53</AndroidSigningStorePass>
    <AndroidSigningKeyAlias>letmetalk</AndroidSigningKeyAlias>
    <AndroidSigningKeyPass>Ke42OgMwldsw53</AndroidSigningKeyPass>
</PropertyGroup>
Comment 3 Jens 2013-10-18 16:48:28 UTC
Created attachment 5173 [details]
requested build.txt
Comment 4 Jonathan Pryor 2013-10-18 17:09:41 UTC
As per IRC discussion, the Build generated from #2 runs without generating the warning/error messages.

It was built with:

   xbuild /p:Configuration=Release /t:SignAndroidPackage Project.csproj

See also: http://docs.xamarin.com/guides/android/advanced_topics/build_process#2.12.signing

Is this just a one-off error? Or is this a bug in XS' "Publish Android Application" support?
Comment 5 Jon Douglas [MSFT] 2017-08-07 20:40:00 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!