admin管理员组

文章数量:1026989

I'm using Bubblewrap to build a Trusted Web Activity (TWA) and expected it to generate the assetlinks.json file as part of the process. However, it doesn't seem to create the file.

Indeed, I used a local keystore for signing for local debugging, but also tested using app signing from the Google Play Console. The Google documentation that says Bubblewrap should generate the assetlinks.json automatically, but it never does.

Is there a step I'm missing, or does Bubblewrap require manual creation of the assetlinks.json file?

Steps to reproduce:

  1. Run bubblewrap init and configure the TWA project.
  2. Use either a local keystore or Play Console app signing.
  3. Run bubblewrap build.

The assetlinks.json file should be generated automatically according to Google ChromeOS docs, although the file is not generated.

Do you have any suggestion?

I'm using Bubblewrap to build a Trusted Web Activity (TWA) and expected it to generate the assetlinks.json file as part of the process. However, it doesn't seem to create the file.

Indeed, I used a local keystore for signing for local debugging, but also tested using app signing from the Google Play Console. The Google documentation that says Bubblewrap should generate the assetlinks.json automatically, but it never does.

Is there a step I'm missing, or does Bubblewrap require manual creation of the assetlinks.json file?

Steps to reproduce:

  1. Run bubblewrap init and configure the TWA project.
  2. Use either a local keystore or Play Console app signing.
  3. Run bubblewrap build.

The assetlinks.json file should be generated automatically according to Google ChromeOS docs, although the file is not generated.

Do you have any suggestion?

  • android
  • google-play
  • android-app-signing
  • trusted-web-activity
  • bubblewrap
Share Improve this question asked Nov 16, 2024 at 11:24 DeleterDeleter 8101 gold badge12 silver badges33 bronze badges 1
  • 1 I found out, in new versions, Bubblewrap doesn't automatically generate the assetlinks.json file during the build step, even though the documentation suggests it might. I need to manually create the file using your app's signing information (SHA256) provided by Google Play (App signing page) or using keytool command on my own local keystore – Deleter Commented Nov 19, 2024 at 12:06
Add a comment  | 

1 Answer 1

Reset to default 0

As I said in the comments, I found out, in new versions, Bubblewrap doesn't automatically generate the assetlinks.json file during the build step, even though the documentation suggests it might.

Thus, I need to manually create the file using your app's signing information (SHA256) provided by Google Play (App signing page) or using keytool command on my own local keystore – Deleter

I'm using Bubblewrap to build a Trusted Web Activity (TWA) and expected it to generate the assetlinks.json file as part of the process. However, it doesn't seem to create the file.

Indeed, I used a local keystore for signing for local debugging, but also tested using app signing from the Google Play Console. The Google documentation that says Bubblewrap should generate the assetlinks.json automatically, but it never does.

Is there a step I'm missing, or does Bubblewrap require manual creation of the assetlinks.json file?

Steps to reproduce:

  1. Run bubblewrap init and configure the TWA project.
  2. Use either a local keystore or Play Console app signing.
  3. Run bubblewrap build.

The assetlinks.json file should be generated automatically according to Google ChromeOS docs, although the file is not generated.

Do you have any suggestion?

I'm using Bubblewrap to build a Trusted Web Activity (TWA) and expected it to generate the assetlinks.json file as part of the process. However, it doesn't seem to create the file.

Indeed, I used a local keystore for signing for local debugging, but also tested using app signing from the Google Play Console. The Google documentation that says Bubblewrap should generate the assetlinks.json automatically, but it never does.

Is there a step I'm missing, or does Bubblewrap require manual creation of the assetlinks.json file?

Steps to reproduce:

  1. Run bubblewrap init and configure the TWA project.
  2. Use either a local keystore or Play Console app signing.
  3. Run bubblewrap build.

The assetlinks.json file should be generated automatically according to Google ChromeOS docs, although the file is not generated.

Do you have any suggestion?

  • android
  • google-play
  • android-app-signing
  • trusted-web-activity
  • bubblewrap
Share Improve this question asked Nov 16, 2024 at 11:24 DeleterDeleter 8101 gold badge12 silver badges33 bronze badges 1
  • 1 I found out, in new versions, Bubblewrap doesn't automatically generate the assetlinks.json file during the build step, even though the documentation suggests it might. I need to manually create the file using your app's signing information (SHA256) provided by Google Play (App signing page) or using keytool command on my own local keystore – Deleter Commented Nov 19, 2024 at 12:06
Add a comment  | 

1 Answer 1

Reset to default 0

As I said in the comments, I found out, in new versions, Bubblewrap doesn't automatically generate the assetlinks.json file during the build step, even though the documentation suggests it might.

Thus, I need to manually create the file using your app's signing information (SHA256) provided by Google Play (App signing page) or using keytool command on my own local keystore – Deleter

本文标签： androidBubblewrap not generating assetlinksjson automaticallyStack Overflow

版权声明：本文标题：android - Bubblewrap not generating assetlinks.json automatically - Stack Overflow 内容由热心网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://it.en369.cn/questions/1745659325a2161791.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。