search

sajith4u / maven-android-plugin

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

[Test application] does not have signature matching target [core application] #408

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Clean install core application
2. Deploy core application to phone
3. Clean install Test application

What is the expected output?
Tests for core application run

What do you see instead?
Failed to execute goal 
com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.4.1:internal
-integration-test (default-internal-integration-test) on project test: Test run 
failed to complete: Permission Denial: starting instrumentation 
ComponentInfo{packagename.core.tests/android.test.InstrumentationTestRunner} 
from pid=14383, uid=14383 not allowed because package packagename.core.tests 
does not have a signature matching the target packagename.core

What version of maven-android-plugin are you using?
3.4.1

What are the complete output lines of "mvn -version" on your machine?
3.0.4

Please provide any additional information below.
I have tried changing <sign><debug> to true/false/both/auto but nothing has 
worked.

Original issue reported on code.google.com by Thomasad...@gmail.com on 18 Jul 2013 at 7:39

GoogleCodeExporter commented 9 years ago 
Here is the jarsigner excerpt from my pom.xml

<plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-jarsigner-plugin</artifactId>
        <version>1.2</version>
        <executions>
            <execution>
                <id>signing</id>
                <goals>
                    <goal>sign</goal>
                </goals>
                <phase>package</phase>
                <inherited>true</inherited>
                <configuration>
                    <archiveDirectory></archiveDirectory>
                    <includes>
                        <include>target/*.apk</include>
                    </includes>
                    <keystore>my-key.keystore</keystore>
                    <storepass>namepass</storepass>
                    <keypass>namepass</keypass>
                    <alias>my_key</alias>
                    <arguments>
                      <argument>-sigalg</argument><argument>MD5withRSA</argument>
                      <argument>-digestalg</argument><argument>SHA1</argument>
                    </arguments>
                </configuration>
            </execution>
        </executions>
      </plugin>

The my-key.keystore is in this same directory as the pom.xml

Original comment by Thomasad...@gmail.com on 18 Jul 2013 at 9:09

GoogleCodeExporter commented 9 years ago 
We are no longer using the issue tracking system on Google Code. Please refile 
this issue on https://github.com/jayway/maven-android-plugin/issues if you 
still have this problem with the latest release of the Android Maven Plugin

Original comment by mosa...@gmail.com on 19 May 2014 at 4:20