问题
I implemented universal linking for my Android app. Everything works fine so far. I click on a universal link and will be immediately redirected to the app. However, I have always used debug for the Digital Asset Links. For the release I need the signing config or the keystore file.
To sign my app I always use a created xxxx.jks file. If I specify this, an error occurs: Error occured while trying to get the SHA-256 fingerprint (See screenshot).
The error is very meaningless. That's why I'm a little confused. Do I use the right file? How do I get a better error description? I always use this file to sign my app for a new release. That doesn't cause any problems.
I already took the SHA-256 fingerprint from the App signature certificate from the Play Console. This doesn't really work properly. Whenever you click on my universal link, the app asks: Should the link be opened with Chrome or with 'MyApp'?
I am grateful for input.
回答1:
Okay, the solution was simple. I just take the SHA256 from the google play console. This one you have to put in your assetlinks.json
Then I build a public beta and it works like expected.
来源：https://stackoverflow.com/questions/59345516/android-generate-digital-asset-link-keystore-file-for-signing-the-app