twa | A tiny web auditor with strong opinions | Cybersecurity library

What you are doing with XML is called shredding. It converts XML data type into a rectangular/relational format. After that you need to join it with the rest of data in some other DB tables.

The easiest way to achieve it is via CTE. And you need to join data/columns from the resultset rs.* with the rest of the DB tables.

Along the following:

Please try the following solution.

Notable notes:

• A proper declaration of the default namespace simplifies XPath expressions across the board. A default namespace doesn't require a prefix.
• It is better not to use // in the XPath expressions. It causes to traverse the entire XML. A fully qualified path is better for performance.
• Adding text() to the XPath expressions for XML elements improves performance.

SQL

According to the documentation, the output of an insert can refer to just the inserted and deleted tables. Using merge is the workaround.

Here is how to restructure with merge

Yes, you will need to add the extra domains to the intent-filter in AndroidManifest.xml.

Using the twa-multi-domain sample, the main domain in the app is www.google.com and github.com and www.wikipedia.com are extra domains. After adding the 2 extra domains, this is how the section on AndroidManifest.xml should look like (lines 13 to 16 are new):

The syntax 0:(n-1) creates a sequence, a single vector of integers going from zero to n-1. However your n is itself a vector, because it is defined as term - time and time is a vector of all integers 0 to 40 (hence it contains 41 elements). So only the first element of n is used to create the sequence. For example if n was c(4,5,10), only the 4 would be used, ignoring 5 and 10, and 0:(n-1) would return c(0,1,2,3).

You would need to redefine the AnU() and TWa() functions. I am not sure exactly what you need but I think you can just replace the line for (k in 0:(n-1)) with for (k in 0:(max(n)-1)). I wanted to test this but I was unable to reproduce your error because the object lx, which is in the formula in both functions, is not defined in your code.

Nowadays, I'd recommend using @bubblewrap/cli to bootstrap the Trusted Web Activity project, as svgomg-twa has been deprecated and replaced by Bubblewrap.

In short, yes, it is possible to integrate in-app-reviews in a Trusted Web Activity.

The general approach is to use a custom schema, like my-app:// that is handled by an Android Activity. This Activity will, in turn, launch the review flow and then finish itself.

There are some caveats though:

• You'll need to check if the all is in "trusted web activity mode" in order to display the link, as it only works when inside a Trusted Web Activity.
• This may also not be compatible with Chrome OS, so if you are also deploying the Trusted Web Activity there, I wouldn't recommend integrating in-app reviews.

Here's a blogpost with more details on how to do it.

Currently, the easiest way to use a Web App on Android TV is by using the WebView. Many PWA features are not supported by the WebView.

Youtube uses Cobalt as the platform to run their app across different platforms. It only supports a subset of HTML, CSS and JavaScript, so it doesn't provide PWA support.

Trusted Web Activity is not currently supported on Android TV. There's an open feature request at http://crbug.com/1054737.

For those interested in Trusted Web Activity support for Android TV, I'd recommend going to that issue and starring the feature request, so the team will have a better idea of the demand and can prioritise.

What may have cause the problem was that I was manipulating the DOM directly by using document.getElementsByClassName within my useEffect function, and then was setting each slide to be at a certain place in the grid, or making the slide invisible. I changed my code so that an array of slides was recorded in state

You can't use the native code in a TWA or PWA, that's the whole point of the native platforms, to use native code when the web don't have a proper equivalent.

With Capacitor you use the same code for web, native iOS and native Android, is up to you if you want to use native iOS and native Android or not, but to use it you have to publish the app on the App store and Play store, the PWA will always use web APIs.