Android - Adding at least one Activity with an ACTION-VIEW intent-filter after Updating SDK version 23
I am getting following tool tip in AndroidManifest.xml
App is not indexable by Google Search; consider adding at least one
Activity with an ACTION-VIEW intent-filler. See issue explanation for
more details.
Adds deep links to get your app into the Google index,
to get installs and traffic to your app from Google Search.
Any one can explain why it is so?
Your Help would be appreciated.
android android-intent android-manifest
add a comment |
I am getting following tool tip in AndroidManifest.xml
App is not indexable by Google Search; consider adding at least one
Activity with an ACTION-VIEW intent-filler. See issue explanation for
more details.
Adds deep links to get your app into the Google index,
to get installs and traffic to your app from Google Search.
Any one can explain why it is so?
Your Help would be appreciated.
android android-intent android-manifest
add a comment |
I am getting following tool tip in AndroidManifest.xml
App is not indexable by Google Search; consider adding at least one
Activity with an ACTION-VIEW intent-filler. See issue explanation for
more details.
Adds deep links to get your app into the Google index,
to get installs and traffic to your app from Google Search.
Any one can explain why it is so?
Your Help would be appreciated.
android android-intent android-manifest
I am getting following tool tip in AndroidManifest.xml
App is not indexable by Google Search; consider adding at least one
Activity with an ACTION-VIEW intent-filler. See issue explanation for
more details.
Adds deep links to get your app into the Google index,
to get installs and traffic to your app from Google Search.
Any one can explain why it is so?
Your Help would be appreciated.
android android-intent android-manifest
android android-intent android-manifest
edited Nov 23 '18 at 10:21
asked Dec 19 '15 at 6:09
Pratik Butani
29.3k25142260
29.3k25142260
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
From official documentation :
To enable Google to crawl your app content and allow users to enter your app from search results, you must add intent filters for the relevant activities in your app manifest. These intent filters allow deep linking to the content in any of your activities. For example, the user might click on a deep link to view a page within a shopping app that describes a product offering that the user is searching for.
Using this link Enabling Deep Links for App Content you'll see how to use it.
And using this Test Your App Indexing Implementation how to test it.
The following XML snippet shows how you might specify an intent filter
in your manifest for deep linking.
<activity
android:name="com.example.android.GizmosActivity"
android:label="@string/title_gizmos" >
<intent-filter android:label="@string/filter_title_viewgizmos">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<!-- Accepts URIs that begin with "http://www.example.com/gizmos” -->
<data android:scheme="http"
android:host="www.example.com"
android:pathPrefix="/gizmos" />
<!-- note that the leading "/" is required for pathPrefix-->
<!-- Accepts URIs that begin with "example://gizmos” -->
<data android:scheme="example"
android:host="gizmos" />
</intent-filter>
</activity>
To test via Android Debug Bridge
$ adb shell am start
-W -a android.intent.action.VIEW
-d <URI> <PACKAGE>
$ adb shell am start
-W -a android.intent.action.VIEW
-d "example://gizmos" com.example.android
4
@user25 scheme is the uri scheme, scheme can be http, https, ftp etc
– Bhargav
Sep 22 '16 at 7:16
28
well all of this for specific apps, then why show that warning? not all apps need this, not all apps are webview of some sites. Google is so annoying..
– user924
Jun 30 '18 at 13:39
21
It can be suppressed anyway with tools:ignore="GoogleAppIndexingWarning"
– ecle
Aug 27 '18 at 2:32
3
Curious that the warning says you need anACTION-VIEW
intent-filter, yet the solution involvesaction.VIEW
. Likewise, following the link in Android Studio takes you to a webpage whereACTION-VIEW
does not appear. The least they could do with obtrusive warnings is give you accurate messages and help pages.
– John Perry
Oct 20 '18 at 16:29
1
@ecle Where does one put this option? / Never mind; I found it: One has to addxmlns:tools="http://schemas.android.com/tools"
to themanifest
tag, then addtools:ignore...
to theapplication
tag.
– John Perry
Oct 20 '18 at 16:31
add a comment |
You can remove the warning by adding the below code in <intent-filter>
inside <activity>
<action android:name="android.intent.action.VIEW" />
1
This work's for me. I think this is the answer what I'm looking for.
– Mahmudur Rahman
Nov 10 '18 at 18:21
This appears to be the correct solution if you don't want to enable app indexing. Rather than just removing the warning viatools:ignore="GoogleAppIndexingWarning"
. I added it as a sibling to<action android:name="android.intent.action.MAIN" />
in the main activity.
– Daniel F
Dec 5 '18 at 12:11
add a comment |
You can remove the warning by adding xmlns:tools="http://schemas.android.com/tools"
to the <manifest>
tag and tools:ignore="GoogleAppIndexingWarning"
to the <application>
tag.
This works for me, and exactly the solution I was looking for.
– Sayan Sil
Nov 27 '18 at 16:03
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%2f34367875%2fandroid-adding-at-least-one-activity-with-an-action-view-intent-filter-after-u%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
From official documentation :
To enable Google to crawl your app content and allow users to enter your app from search results, you must add intent filters for the relevant activities in your app manifest. These intent filters allow deep linking to the content in any of your activities. For example, the user might click on a deep link to view a page within a shopping app that describes a product offering that the user is searching for.
Using this link Enabling Deep Links for App Content you'll see how to use it.
And using this Test Your App Indexing Implementation how to test it.
The following XML snippet shows how you might specify an intent filter
in your manifest for deep linking.
<activity
android:name="com.example.android.GizmosActivity"
android:label="@string/title_gizmos" >
<intent-filter android:label="@string/filter_title_viewgizmos">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<!-- Accepts URIs that begin with "http://www.example.com/gizmos” -->
<data android:scheme="http"
android:host="www.example.com"
android:pathPrefix="/gizmos" />
<!-- note that the leading "/" is required for pathPrefix-->
<!-- Accepts URIs that begin with "example://gizmos” -->
<data android:scheme="example"
android:host="gizmos" />
</intent-filter>
</activity>
To test via Android Debug Bridge
$ adb shell am start
-W -a android.intent.action.VIEW
-d <URI> <PACKAGE>
$ adb shell am start
-W -a android.intent.action.VIEW
-d "example://gizmos" com.example.android
4
@user25 scheme is the uri scheme, scheme can be http, https, ftp etc
– Bhargav
Sep 22 '16 at 7:16
28
well all of this for specific apps, then why show that warning? not all apps need this, not all apps are webview of some sites. Google is so annoying..
– user924
Jun 30 '18 at 13:39
21
It can be suppressed anyway with tools:ignore="GoogleAppIndexingWarning"
– ecle
Aug 27 '18 at 2:32
3
Curious that the warning says you need anACTION-VIEW
intent-filter, yet the solution involvesaction.VIEW
. Likewise, following the link in Android Studio takes you to a webpage whereACTION-VIEW
does not appear. The least they could do with obtrusive warnings is give you accurate messages and help pages.
– John Perry
Oct 20 '18 at 16:29
1
@ecle Where does one put this option? / Never mind; I found it: One has to addxmlns:tools="http://schemas.android.com/tools"
to themanifest
tag, then addtools:ignore...
to theapplication
tag.
– John Perry
Oct 20 '18 at 16:31
add a comment |
From official documentation :
To enable Google to crawl your app content and allow users to enter your app from search results, you must add intent filters for the relevant activities in your app manifest. These intent filters allow deep linking to the content in any of your activities. For example, the user might click on a deep link to view a page within a shopping app that describes a product offering that the user is searching for.
Using this link Enabling Deep Links for App Content you'll see how to use it.
And using this Test Your App Indexing Implementation how to test it.
The following XML snippet shows how you might specify an intent filter
in your manifest for deep linking.
<activity
android:name="com.example.android.GizmosActivity"
android:label="@string/title_gizmos" >
<intent-filter android:label="@string/filter_title_viewgizmos">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<!-- Accepts URIs that begin with "http://www.example.com/gizmos” -->
<data android:scheme="http"
android:host="www.example.com"
android:pathPrefix="/gizmos" />
<!-- note that the leading "/" is required for pathPrefix-->
<!-- Accepts URIs that begin with "example://gizmos” -->
<data android:scheme="example"
android:host="gizmos" />
</intent-filter>
</activity>
To test via Android Debug Bridge
$ adb shell am start
-W -a android.intent.action.VIEW
-d <URI> <PACKAGE>
$ adb shell am start
-W -a android.intent.action.VIEW
-d "example://gizmos" com.example.android
4
@user25 scheme is the uri scheme, scheme can be http, https, ftp etc
– Bhargav
Sep 22 '16 at 7:16
28
well all of this for specific apps, then why show that warning? not all apps need this, not all apps are webview of some sites. Google is so annoying..
– user924
Jun 30 '18 at 13:39
21
It can be suppressed anyway with tools:ignore="GoogleAppIndexingWarning"
– ecle
Aug 27 '18 at 2:32
3
Curious that the warning says you need anACTION-VIEW
intent-filter, yet the solution involvesaction.VIEW
. Likewise, following the link in Android Studio takes you to a webpage whereACTION-VIEW
does not appear. The least they could do with obtrusive warnings is give you accurate messages and help pages.
– John Perry
Oct 20 '18 at 16:29
1
@ecle Where does one put this option? / Never mind; I found it: One has to addxmlns:tools="http://schemas.android.com/tools"
to themanifest
tag, then addtools:ignore...
to theapplication
tag.
– John Perry
Oct 20 '18 at 16:31
add a comment |
From official documentation :
To enable Google to crawl your app content and allow users to enter your app from search results, you must add intent filters for the relevant activities in your app manifest. These intent filters allow deep linking to the content in any of your activities. For example, the user might click on a deep link to view a page within a shopping app that describes a product offering that the user is searching for.
Using this link Enabling Deep Links for App Content you'll see how to use it.
And using this Test Your App Indexing Implementation how to test it.
The following XML snippet shows how you might specify an intent filter
in your manifest for deep linking.
<activity
android:name="com.example.android.GizmosActivity"
android:label="@string/title_gizmos" >
<intent-filter android:label="@string/filter_title_viewgizmos">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<!-- Accepts URIs that begin with "http://www.example.com/gizmos” -->
<data android:scheme="http"
android:host="www.example.com"
android:pathPrefix="/gizmos" />
<!-- note that the leading "/" is required for pathPrefix-->
<!-- Accepts URIs that begin with "example://gizmos” -->
<data android:scheme="example"
android:host="gizmos" />
</intent-filter>
</activity>
To test via Android Debug Bridge
$ adb shell am start
-W -a android.intent.action.VIEW
-d <URI> <PACKAGE>
$ adb shell am start
-W -a android.intent.action.VIEW
-d "example://gizmos" com.example.android
From official documentation :
To enable Google to crawl your app content and allow users to enter your app from search results, you must add intent filters for the relevant activities in your app manifest. These intent filters allow deep linking to the content in any of your activities. For example, the user might click on a deep link to view a page within a shopping app that describes a product offering that the user is searching for.
Using this link Enabling Deep Links for App Content you'll see how to use it.
And using this Test Your App Indexing Implementation how to test it.
The following XML snippet shows how you might specify an intent filter
in your manifest for deep linking.
<activity
android:name="com.example.android.GizmosActivity"
android:label="@string/title_gizmos" >
<intent-filter android:label="@string/filter_title_viewgizmos">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<!-- Accepts URIs that begin with "http://www.example.com/gizmos” -->
<data android:scheme="http"
android:host="www.example.com"
android:pathPrefix="/gizmos" />
<!-- note that the leading "/" is required for pathPrefix-->
<!-- Accepts URIs that begin with "example://gizmos” -->
<data android:scheme="example"
android:host="gizmos" />
</intent-filter>
</activity>
To test via Android Debug Bridge
$ adb shell am start
-W -a android.intent.action.VIEW
-d <URI> <PACKAGE>
$ adb shell am start
-W -a android.intent.action.VIEW
-d "example://gizmos" com.example.android
edited May 12 '16 at 14:37
Philip Belgrave-Herbert
2,68422131
2,68422131
answered Dec 19 '15 at 8:30
Mk.Sl.
1,3591710
1,3591710
4
@user25 scheme is the uri scheme, scheme can be http, https, ftp etc
– Bhargav
Sep 22 '16 at 7:16
28
well all of this for specific apps, then why show that warning? not all apps need this, not all apps are webview of some sites. Google is so annoying..
– user924
Jun 30 '18 at 13:39
21
It can be suppressed anyway with tools:ignore="GoogleAppIndexingWarning"
– ecle
Aug 27 '18 at 2:32
3
Curious that the warning says you need anACTION-VIEW
intent-filter, yet the solution involvesaction.VIEW
. Likewise, following the link in Android Studio takes you to a webpage whereACTION-VIEW
does not appear. The least they could do with obtrusive warnings is give you accurate messages and help pages.
– John Perry
Oct 20 '18 at 16:29
1
@ecle Where does one put this option? / Never mind; I found it: One has to addxmlns:tools="http://schemas.android.com/tools"
to themanifest
tag, then addtools:ignore...
to theapplication
tag.
– John Perry
Oct 20 '18 at 16:31
add a comment |
4
@user25 scheme is the uri scheme, scheme can be http, https, ftp etc
– Bhargav
Sep 22 '16 at 7:16
28
well all of this for specific apps, then why show that warning? not all apps need this, not all apps are webview of some sites. Google is so annoying..
– user924
Jun 30 '18 at 13:39
21
It can be suppressed anyway with tools:ignore="GoogleAppIndexingWarning"
– ecle
Aug 27 '18 at 2:32
3
Curious that the warning says you need anACTION-VIEW
intent-filter, yet the solution involvesaction.VIEW
. Likewise, following the link in Android Studio takes you to a webpage whereACTION-VIEW
does not appear. The least they could do with obtrusive warnings is give you accurate messages and help pages.
– John Perry
Oct 20 '18 at 16:29
1
@ecle Where does one put this option? / Never mind; I found it: One has to addxmlns:tools="http://schemas.android.com/tools"
to themanifest
tag, then addtools:ignore...
to theapplication
tag.
– John Perry
Oct 20 '18 at 16:31
4
4
@user25 scheme is the uri scheme, scheme can be http, https, ftp etc
– Bhargav
Sep 22 '16 at 7:16
@user25 scheme is the uri scheme, scheme can be http, https, ftp etc
– Bhargav
Sep 22 '16 at 7:16
28
28
well all of this for specific apps, then why show that warning? not all apps need this, not all apps are webview of some sites. Google is so annoying..
– user924
Jun 30 '18 at 13:39
well all of this for specific apps, then why show that warning? not all apps need this, not all apps are webview of some sites. Google is so annoying..
– user924
Jun 30 '18 at 13:39
21
21
It can be suppressed anyway with tools:ignore="GoogleAppIndexingWarning"
– ecle
Aug 27 '18 at 2:32
It can be suppressed anyway with tools:ignore="GoogleAppIndexingWarning"
– ecle
Aug 27 '18 at 2:32
3
3
Curious that the warning says you need an
ACTION-VIEW
intent-filter, yet the solution involves action.VIEW
. Likewise, following the link in Android Studio takes you to a webpage where ACTION-VIEW
does not appear. The least they could do with obtrusive warnings is give you accurate messages and help pages.– John Perry
Oct 20 '18 at 16:29
Curious that the warning says you need an
ACTION-VIEW
intent-filter, yet the solution involves action.VIEW
. Likewise, following the link in Android Studio takes you to a webpage where ACTION-VIEW
does not appear. The least they could do with obtrusive warnings is give you accurate messages and help pages.– John Perry
Oct 20 '18 at 16:29
1
1
@ecle Where does one put this option? / Never mind; I found it: One has to add
xmlns:tools="http://schemas.android.com/tools"
to the manifest
tag, then add tools:ignore...
to the application
tag.– John Perry
Oct 20 '18 at 16:31
@ecle Where does one put this option? / Never mind; I found it: One has to add
xmlns:tools="http://schemas.android.com/tools"
to the manifest
tag, then add tools:ignore...
to the application
tag.– John Perry
Oct 20 '18 at 16:31
add a comment |
You can remove the warning by adding the below code in <intent-filter>
inside <activity>
<action android:name="android.intent.action.VIEW" />
1
This work's for me. I think this is the answer what I'm looking for.
– Mahmudur Rahman
Nov 10 '18 at 18:21
This appears to be the correct solution if you don't want to enable app indexing. Rather than just removing the warning viatools:ignore="GoogleAppIndexingWarning"
. I added it as a sibling to<action android:name="android.intent.action.MAIN" />
in the main activity.
– Daniel F
Dec 5 '18 at 12:11
add a comment |
You can remove the warning by adding the below code in <intent-filter>
inside <activity>
<action android:name="android.intent.action.VIEW" />
1
This work's for me. I think this is the answer what I'm looking for.
– Mahmudur Rahman
Nov 10 '18 at 18:21
This appears to be the correct solution if you don't want to enable app indexing. Rather than just removing the warning viatools:ignore="GoogleAppIndexingWarning"
. I added it as a sibling to<action android:name="android.intent.action.MAIN" />
in the main activity.
– Daniel F
Dec 5 '18 at 12:11
add a comment |
You can remove the warning by adding the below code in <intent-filter>
inside <activity>
<action android:name="android.intent.action.VIEW" />
You can remove the warning by adding the below code in <intent-filter>
inside <activity>
<action android:name="android.intent.action.VIEW" />
answered Oct 22 '18 at 17:17
user
680312
680312
1
This work's for me. I think this is the answer what I'm looking for.
– Mahmudur Rahman
Nov 10 '18 at 18:21
This appears to be the correct solution if you don't want to enable app indexing. Rather than just removing the warning viatools:ignore="GoogleAppIndexingWarning"
. I added it as a sibling to<action android:name="android.intent.action.MAIN" />
in the main activity.
– Daniel F
Dec 5 '18 at 12:11
add a comment |
1
This work's for me. I think this is the answer what I'm looking for.
– Mahmudur Rahman
Nov 10 '18 at 18:21
This appears to be the correct solution if you don't want to enable app indexing. Rather than just removing the warning viatools:ignore="GoogleAppIndexingWarning"
. I added it as a sibling to<action android:name="android.intent.action.MAIN" />
in the main activity.
– Daniel F
Dec 5 '18 at 12:11
1
1
This work's for me. I think this is the answer what I'm looking for.
– Mahmudur Rahman
Nov 10 '18 at 18:21
This work's for me. I think this is the answer what I'm looking for.
– Mahmudur Rahman
Nov 10 '18 at 18:21
This appears to be the correct solution if you don't want to enable app indexing. Rather than just removing the warning via
tools:ignore="GoogleAppIndexingWarning"
. I added it as a sibling to <action android:name="android.intent.action.MAIN" />
in the main activity.– Daniel F
Dec 5 '18 at 12:11
This appears to be the correct solution if you don't want to enable app indexing. Rather than just removing the warning via
tools:ignore="GoogleAppIndexingWarning"
. I added it as a sibling to <action android:name="android.intent.action.MAIN" />
in the main activity.– Daniel F
Dec 5 '18 at 12:11
add a comment |
You can remove the warning by adding xmlns:tools="http://schemas.android.com/tools"
to the <manifest>
tag and tools:ignore="GoogleAppIndexingWarning"
to the <application>
tag.
This works for me, and exactly the solution I was looking for.
– Sayan Sil
Nov 27 '18 at 16:03
add a comment |
You can remove the warning by adding xmlns:tools="http://schemas.android.com/tools"
to the <manifest>
tag and tools:ignore="GoogleAppIndexingWarning"
to the <application>
tag.
This works for me, and exactly the solution I was looking for.
– Sayan Sil
Nov 27 '18 at 16:03
add a comment |
You can remove the warning by adding xmlns:tools="http://schemas.android.com/tools"
to the <manifest>
tag and tools:ignore="GoogleAppIndexingWarning"
to the <application>
tag.
You can remove the warning by adding xmlns:tools="http://schemas.android.com/tools"
to the <manifest>
tag and tools:ignore="GoogleAppIndexingWarning"
to the <application>
tag.
answered Nov 5 '18 at 12:46
Pat Lee
38924
38924
This works for me, and exactly the solution I was looking for.
– Sayan Sil
Nov 27 '18 at 16:03
add a comment |
This works for me, and exactly the solution I was looking for.
– Sayan Sil
Nov 27 '18 at 16:03
This works for me, and exactly the solution I was looking for.
– Sayan Sil
Nov 27 '18 at 16:03
This works for me, and exactly the solution I was looking for.
– Sayan Sil
Nov 27 '18 at 16:03
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f34367875%2fandroid-adding-at-least-one-activity-with-an-action-view-intent-filter-after-u%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