Hello, I found a problem with the WebViewStringChange block in the WebViewer component
I was able to run the site from the asset (in iOS) but did not get a response from WebViewStringChange.
(It works fully on Android - you should get the text you typed on the keyboard in label 1)
In addition, I noticed that no alerts are opened from the site (this should open a window when you click on the button displayed in the site viewer) HTML.aia (2.7 KB)
Hmm. WebViewStringChange should have worked okay. Regarding the alert box, I think that is something separate we'll have to implement as the WKWebView doesn't do this natively--it's up to the browser/app to provide it. I've filed an issue with the corresponding AIA attached.
Your HTML code has a couple of minor syntax errors that do not have an effect on it's purpose.
Are you sure the paths to the file are correct? On Android we are now using: http://localhost/myhtml.html
For both companion and build.
Alert works in a WebViewer on Android
The problem was fixed after the last update (2.60.1) but I noticed that if I use one of the following characters (on the keyboard): space, ', ", ₪, {,}, €, £, ^,%
(in addition it also happens with characters in languages Miscellaneous and there may be other characters that this problem happens with) then I get this error:
I noticed that if I remove one of the problematic characters from the keyboard (after getting the initial error) I will get this error. (But this only happens in some characters):
Thanks for the answer, it works now
I checked the same thing on Android and instead of a space character I get the + character (in iOS this does not happen).
Android:
Although the problem can be easily solved, I think the initial problem needs to be fixed, as there is a different response between the platforms and we want the application to behave as similarly as possible on both platforms.
I believe the Android implementation is correct here because typically when you convert a string into a query string, spaces are replaced by +'s (see for example conducting a search in your favorite search engine). The iOS API for URI escaping might not be processing spaces but I'd have to check the documentation.