StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19471865
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-19T22:29:12.483
FavoriteCount
0
LastActivityDate
2013-10-19T22:29:12.483
LastEditDate
LastEditorUserId
0
OwnerUserId
1122776
ParentId
19235489
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
After over a month of research I've concluded that setting a cookie in android versions greater than 2.3 is not possible in a webview where the file is on the localhost (read directly from the assets folder). I went through many alternatives to to using cookie storage, including using HTML's localstorage. The whole issue here, I am led to believe, is security. If I were to create a cookie or localstorage on the localhost, then other apps could access that storage, thus is a major security threat. My ultimate problem was trying to bridge the webview with two-way communication with java and also having a place to store data during the process. My solution was to take advantage of the JavascriptInterface The idea is as follows: <ul> <li>Parse data to function in javascript</li> <li>Javascript calls a special javascript function e.g. "setData(myDataName, myData)"</li> <li>Java has a function which listens to this, and will take arguments set by javscript, and can also return values to javascript.</li> <li>Once data is parsed to Java, java stores this in a series of files in assets.</li> <li>When javascript function "getData(myDataName)" is called, the data is returned by the same kind of method by Java.</li> </ul> I found this very useful: <a href="http://developer.android.com/reference/android/webkit/WebView.html#addJavascriptInterface%28java.lang.Object,%20java.lang.String%29" rel="nofollow">Android JavascriptInterface Documentation</a>, <a href="http://www.jasonshah.com/handling-android-2-3-webviews-broken-addjavascriptinterface/" rel="nofollow">Handling JavascriptInterface in Android 2.3</a> The only major 'hang-ups' come with a what I found was a <a href="http://code.google.com/p/android/issues/detail?id=12987" rel="nofollow">fairly serious bug</a> in Android 2.3 (fixed in 3.0) which effectively broke the JavascriptInterface. The second link above describes the best workaround I have found. Here is an example of how to get the two-way communication working (it's very messy, but it works): Custom webinterface class: <pre><code>public class webViewInterface { //@JavascriptInterface //for SDK 12+ public String showToast(String myText) { Toast.makeText(context, myText, Toast.LENGTH_LONG).show(); return myText; } } </code></pre> Main class: protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); <pre><code>setContentView(R.layout.activity_main); engine = (WebView) findViewById(R.id.web_engine); context = this; WebSettings webSettings = engine.getSettings(); webSettings.setJavaScriptEnabled(true); engine.setWebViewClient(new WebViewClient()); engine.loadUrl("file:///android_asset/" + page); boolean javascriptInterfaceBroken = false; try { if (Build.VERSION.RELEASE.startsWith("2.3")) { javascriptInterfaceBroken = true; } } catch (Exception e) { // Ignore, and assume user javascript interface is working correctly. } // Add javascript interface only if it's not broken // @TODO: write the workaround for < 2.3 devices if (!javascriptInterfaceBroken) { engine.addJavascriptInterface(new webViewInterface(), "MainActivityInterface"); } //disables text selection engine.setOnLongClickListener(new View.OnLongClickListener() { public boolean onLongClick(View v) { return true; } }); } </code></pre> HTML: <pre><code><html> <head> </head> <body> <input type="button" value="Say hello" onClick="showAndroidToast();" /> <script type="text/javascript"> function showAndroidToast() { document.write(MainActivityInterface.showToast("eureka!")); } </script> </body> </html> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid webview cookie returns null
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USkirgy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAndroid webview cookie returns null
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.