nextcloud / nextcloud/notes-android

Dependency verification fails for "Android-SingleSignOn-1.3.0.module"

Open
#2,351 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
Java
Stars
1.1k
Forks
168
Avg merge
1d 17h
Merged PRs (30d)
31

Description

This issue respects the following points:
Describe the bug

Hi there,

when trying to build the app from scratch (./gradlew build) I'm getting this error:

 Dependency verification failed for configuration ':app:devDebugCompileClasspath':
    - On artifact Android-SingleSignOn-1.3.0.module (com.github.nextcloud:Android-SingleSignOn:1.3.0) multiple problems reported:
        - in repository 'maven': artifact is not signed
        - in repository 'maven': expected a 'sha256' checksum of 'b36d6dc843a8881603fd3019a6bdacecb97e46028e984634566c00319519b436' but was '73dbcbfa90a0be5988fab0de8a0850eafdac005e781f91f4307f0035e1644aa3'

By adjusting this block ...

https://github.com/nextcloud/notes-android/blob/2d87223b491dc0a27f28b0f0b70191cb755032d1/gradle/verification-metadata.xml#L3592-L3594

... accordingly ...

<artifact name="Android-SingleSignOn-1.3.0.module">
  <sha256 value="73dbcbfa90a0be5988fab0de8a0850eafdac005e781f91f4307f0035e1644aa3" origin="Generated by Gradle" reason="Artifact is not signed"/>
</artifact>

... the build finishes successfully.

I wonder why there's a discrepancy regarding the version-controlled checksum versus the actual one.

Thanks!

Expected behavior

No response

Notes Android version

n/a

Notes server version

n/a

Nextcloud Android version

n/a

Nextcloud version

n/a

Device

n/a

Android Version

n/a

App Store
  • Google Play Store
  • F-Droid
  • Huawei App Gallery
Stacktrace

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with gradle/verification-metadata.xml around the referenced lines and reproduce the failure with ./gradlew build. Verify the Android-SingleSignOn-1.3.0.module checksum and update the metadata only if appropriate; done means the build completes without dependency verification errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.