![]() ![]() Looking at the output from adb shell dumpsys package domain-preferred-apps the original signed apk is Package: ĭomains: letsdraw.fun Interestingly, they're slightly different sizes. Both of these APKs were downloaded from Google Play, one "original" and one "derived", so they should be identical apart from the signing. The original signed APK and Google Play signed APK can be downloaded from here. I'm writing out the SHA256 fingerprint in logcat from the live release version to double check it's correct and it all looks fine. Instead, I get a dialog asking which app should open the link. Here's an example URL, that when clicked in Android should open the app, which it does for a local build, but not in the Google Play version. I've also downloaded a derived APK from Google Play and made sure that the fingerprint matches that in the assetlinks.json file. I've added the SHA-256 certificate fingerprint from the app signing certificate listed on Google Play to my assetlinks.json so it contains the fingerprint from both the local and Google Play versions. I use "App Signing by Google Play" and understand that the release APK is signed by Google and has a different signature. ![]() With the Google Play version, I get a dialog asking which app should open the link. The applinks work fine when running debug and release versions from my computer but don't work for the version downloaded from Google Play. ![]()
0 Comments
Leave a Reply. |