google / google/app-metadata-encoder

SEVERE: Failed to encrypt metadata

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Description

I generated a key set through Tink and extracted the public key public.bin. When I used Java version "1.8.0_111" to execute it
Jdk1.8.0_111/bin/Java - jar app_metadata_encoder_Java8. jar encoding/ App debug. apk -- metadata=drm. packagename="com. xxx. heater" -- metadata=drm. name="xx" -- metadata=drm. version="1.2.3" -- type=drm -- encryption="com. Google. play"=/public. bin -- output/ Mapk.apk
Prompt Exception SEVERE: Failed to encrypt metadata
Public.bin generates the following instructions through tink
Tinkey create keyset\
--Key template DHKEM_X25519_HKDF-SHA256_HKDF-SHA256AES_256_GCM\
--Out format binary\
--Out my_generated_key.bin
Tinkey create public keyset\
--In format binary\
--In my_generated_key.bin\
--Out format binary\
--Out public.bin

But when I use https://www.gstatic.com/play-apps-publisher/drm-metadata/prod/play_key.bin Time
The execution of write commands in Java version "1.8.0_111" is normal,
For some reasons, our production environment can only use Java version "1.8.0_111"
So I would like to inquire why this exception is triggered and how play_key.bin is generated

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.