i have followed all the steps of trusted web activity but still address bar is visible using chrome dev..how...
This is the screeenshot of our android app but when it opens the address bar is visible as shown how to hide that url(address bar) using trusted web activity?
screenshot here
we have also used Chrome Dev as our default browser but it is not wroking every time when we open the android application. please suggest solution for this.
thanks in advance!
angular
google-chrome-devtools trusted-web-activity asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
add a comment |
This is the screeenshot of our android app but when it opens the address bar is visible as shown how to hide that url(address bar) using trusted web activity?
screenshot here
we have also used Chrome Dev as our default browser but it is not wroking every time when we open the android application. please suggest solution for this.
thanks in advance!
angular
google-chrome-devtools trusted-web-activity asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
There's no screenshot attached, can you add it please?
– JakeSteam
Oct 26 '18 at 9:28
click on hyperlinked screenshot here
– Asmita Patil
Oct 26 '18 at 9:57
add a comment |
This is the screeenshot of our android app but when it opens the address bar is visible as shown how to hide that url(address bar) using trusted web activity?
screenshot here
we have also used Chrome Dev as our default browser but it is not wroking every time when we open the android application. please suggest solution for this.
thanks in advance!
angular
google-chrome-devtools trusted-web-activity asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
This is the screeenshot of our android app but when it opens the address bar is visible as shown how to hide that url(address bar) using trusted web activity?
screenshot here
we have also used Chrome Dev as our default browser but it is not wroking every time when we open the android application. please suggest solution for this.
thanks in advance!
angular
google-chrome-devtools trusted-web-activity angular
google-chrome-devtools trusted-web-activity asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
edited Oct 26 '18 at 9:33
Asmita Patil
asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
asked Oct 26 '18 at 9:22
Asmita PatilAsmita Patil
12
12
There's no screenshot attached, can you add it please?
– JakeSteam
Oct 26 '18 at 9:28
click on hyperlinked screenshot here
– Asmita Patil
Oct 26 '18 at 9:57
add a comment |
There's no screenshot attached, can you add it please?
– JakeSteam
Oct 26 '18 at 9:28
click on hyperlinked screenshot here
– Asmita Patil
Oct 26 '18 at 9:57
There's no screenshot attached, can you add it please?
– JakeSteam
Oct 26 '18 at 9:28
There's no screenshot attached, can you add it please?
– JakeSteam
Oct 26 '18 at 9:28
click on hyperlinked screenshot here
– Asmita Patil
Oct 26 '18 at 9:57
click on hyperlinked screenshot here
– Asmita Patil
Oct 26 '18 at 9:57
add a comment |
1 Answer
1
active
oldest
votes
Google needs to verify that the owner of the website and the owner of the app is the same.
In order to perform this verification it will look for an assetlinks.json at the location /.well-known/assetlinks.json
This assetlinks.json should contain the sha256 of the corresponding android app along with the package_name, namespace and some other information as shown here.
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "org.chromium.twa.svgomg",
"sha256_cert_fingerprints": [
"82:04:C5:DB:19:A8:B9:8A:27:14:F0:3E:F5:23:2C:6B:B6:B9:63:10:F2:F9:CD:44:72:AA:C6:7E:09:E1:1C:47",
"91:45:8F:34:E3:13:E4:58:1C:12:21:7A:FD:1E:BD:5C:BE:9B:DE:2C:1E:57:DC:0D:2B:0E:91:1D:A6:36:CA:E8"
]
}
}]
You will also need to update the AndroidManifest.xml as shown below.
<application>
...
<meta-data android:name="asset_statements"
android:resource="@string/asset_statements" />
...
</application>
For this to work we need to add the asset_statements in the strings.xml file as below.
<string name="asset_statements">
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "web",
"site": "https://svgomg.firebaseapp.com"}
}]
</string>
back slashes are compulsory.
After all this is done make sure that you are targetting chrome dev cause as of Chrome 70, TWA is not supported.
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53005527%2fi-have-followed-all-the-steps-of-trusted-web-activity-but-still-address-bar-is-v%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Google needs to verify that the owner of the website and the owner of the app is the same.
In order to perform this verification it will look for an assetlinks.json at the location /.well-known/assetlinks.json
This assetlinks.json should contain the sha256 of the corresponding android app along with the package_name, namespace and some other information as shown here.
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "org.chromium.twa.svgomg",
"sha256_cert_fingerprints": [
"82:04:C5:DB:19:A8:B9:8A:27:14:F0:3E:F5:23:2C:6B:B6:B9:63:10:F2:F9:CD:44:72:AA:C6:7E:09:E1:1C:47",
"91:45:8F:34:E3:13:E4:58:1C:12:21:7A:FD:1E:BD:5C:BE:9B:DE:2C:1E:57:DC:0D:2B:0E:91:1D:A6:36:CA:E8"
]
}
}]
You will also need to update the AndroidManifest.xml as shown below.
<application>
...
<meta-data android:name="asset_statements"
android:resource="@string/asset_statements" />
...
</application>
For this to work we need to add the asset_statements in the strings.xml file as below.
<string name="asset_statements">
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "web",
"site": "https://svgomg.firebaseapp.com"}
}]
</string>
back slashes are compulsory.
After all this is done make sure that you are targetting chrome dev cause as of Chrome 70, TWA is not supported.
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
add a comment |
Google needs to verify that the owner of the website and the owner of the app is the same.
In order to perform this verification it will look for an assetlinks.json at the location /.well-known/assetlinks.json
This assetlinks.json should contain the sha256 of the corresponding android app along with the package_name, namespace and some other information as shown here.
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "org.chromium.twa.svgomg",
"sha256_cert_fingerprints": [
"82:04:C5:DB:19:A8:B9:8A:27:14:F0:3E:F5:23:2C:6B:B6:B9:63:10:F2:F9:CD:44:72:AA:C6:7E:09:E1:1C:47",
"91:45:8F:34:E3:13:E4:58:1C:12:21:7A:FD:1E:BD:5C:BE:9B:DE:2C:1E:57:DC:0D:2B:0E:91:1D:A6:36:CA:E8"
]
}
}]
You will also need to update the AndroidManifest.xml as shown below.
<application>
...
<meta-data android:name="asset_statements"
android:resource="@string/asset_statements" />
...
</application>
For this to work we need to add the asset_statements in the strings.xml file as below.
<string name="asset_statements">
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "web",
"site": "https://svgomg.firebaseapp.com"}
}]
</string>
back slashes are compulsory.
After all this is done make sure that you are targetting chrome dev cause as of Chrome 70, TWA is not supported.
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
add a comment |
Google needs to verify that the owner of the website and the owner of the app is the same.
In order to perform this verification it will look for an assetlinks.json at the location /.well-known/assetlinks.json
This assetlinks.json should contain the sha256 of the corresponding android app along with the package_name, namespace and some other information as shown here.
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "org.chromium.twa.svgomg",
"sha256_cert_fingerprints": [
"82:04:C5:DB:19:A8:B9:8A:27:14:F0:3E:F5:23:2C:6B:B6:B9:63:10:F2:F9:CD:44:72:AA:C6:7E:09:E1:1C:47",
"91:45:8F:34:E3:13:E4:58:1C:12:21:7A:FD:1E:BD:5C:BE:9B:DE:2C:1E:57:DC:0D:2B:0E:91:1D:A6:36:CA:E8"
]
}
}]
You will also need to update the AndroidManifest.xml as shown below.
<application>
...
<meta-data android:name="asset_statements"
android:resource="@string/asset_statements" />
...
</application>
For this to work we need to add the asset_statements in the strings.xml file as below.
<string name="asset_statements">
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "web",
"site": "https://svgomg.firebaseapp.com"}
}]
</string>
back slashes are compulsory.
After all this is done make sure that you are targetting chrome dev cause as of Chrome 70, TWA is not supported.
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
Google needs to verify that the owner of the website and the owner of the app is the same.
In order to perform this verification it will look for an assetlinks.json at the location /.well-known/assetlinks.json
This assetlinks.json should contain the sha256 of the corresponding android app along with the package_name, namespace and some other information as shown here.
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "org.chromium.twa.svgomg",
"sha256_cert_fingerprints": [
"82:04:C5:DB:19:A8:B9:8A:27:14:F0:3E:F5:23:2C:6B:B6:B9:63:10:F2:F9:CD:44:72:AA:C6:7E:09:E1:1C:47",
"91:45:8F:34:E3:13:E4:58:1C:12:21:7A:FD:1E:BD:5C:BE:9B:DE:2C:1E:57:DC:0D:2B:0E:91:1D:A6:36:CA:E8"
]
}
}]
You will also need to update the AndroidManifest.xml as shown below.
<application>
...
<meta-data android:name="asset_statements"
android:resource="@string/asset_statements" />
...
</application>
For this to work we need to add the asset_statements in the strings.xml file as below.
<string name="asset_statements">
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "web",
"site": "https://svgomg.firebaseapp.com"}
}]
</string>
back slashes are compulsory.
After all this is done make sure that you are targetting chrome dev cause as of Chrome 70, TWA is not supported.
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
edited Nov 14 '18 at 6:35
Raghbendra Nayak
1,15521231
1,15521231
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
answered Nov 14 '18 at 4:22
Mohammed AliMohammed Ali
2316
2316
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53005527%2fi-have-followed-all-the-steps-of-trusted-web-activity-but-still-address-bar-is-v%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There's no screenshot attached, can you add it please?
– JakeSteam
Oct 26 '18 at 9:28
click on hyperlinked screenshot here
– Asmita Patil
Oct 26 '18 at 9:57