Hi all,these observations apply to the Sandbox.In my app, I do a local receipt validation on startup. Apple's documentation "Validating Receipts Locally" says:"If validation fails in iOS, use the SKReceiptRefreshRequest class to refresh the receipt"If I install the app on a new device, receipt validation always fails because there is no local receipt (yet) on the device. But if I use a SKReceiptRefreshRequest, it will prompt the user with a iTunes login. So any time a user installs the app on a new device, they will receive this prompt, which could be confusing.What's the recommendation here? Add an own prompt before the SKReceiptRefreshRequest that explains why the login is required?Thanks,Markus

Hi,in my Catalyst app, a UITableView can be scrolled with two fingers on the trackpad. What doesn't work is dragging a mouse over it while clicking the mouse button. Is this supposed to work? In places where I use UIGestureRecognizers, they work with mouse drags.Thanks,Markus

I created a login webpage that disables the "Login" button as long as user name and password have not been filled in yet: <script type="text/javascript" language="javascript"> function checkform() { var f = document.forms["theform"].elements; var cansubmit = true; for (var i = 0; i < f.length; i++) { if (f[i].value.length == 0) cansubmit = false; } document.getElementById('submitbutton').disabled = !cansubmit; } </script> <form name="theform"> <input id="user-text-field" type="text" type="email" autocomplete="username" onKeyup="checkform()" /> <input id="password-text-field" type="password" autocomplete="current-password" onKeyup="checkform()" /> <input id="submitbutton" type="submit" disabled="disabled" value="Login" /> </form> I use an WkWebView to display the page. It works fine when manually entering user name or password. However, if I use the autocomplete function of iOS to fill in user name and password, the "Login" button stays disabled. It looks like in case of autocomplete, the keyup event is not generated. In Safari, it works correctly. Is this an iOS bug? Any way to work around it?