I wasn't aware that libxslt (and also libexslt apparently) is public on iOS; that's useful to know. (I've used XSLT a fair bit over the years but always on the server side.) You really need to determine whether or not you need XSLT 2 functionality. I suspect that you don't, because a bit of googling finds StackOverflow answers saying that .NET doesn't support XSLT 2. If you actually do... I don't really know what to suggest, except fixing the XSLT to not need the version 2 features. Otherwise, everything boils down to libxslt in the end. So your choice is between Swift -> Javascript -> C -> libxslt -> C -> Javascript -> Swift Swift -> C -> libxslt -> C -> Swift Some of those steps will involve serialising / deserialising XML text to/from XML object representations. Personally, I'd choose the second option. Swift/C interop is pretty good. If you've not done it before - now's your chance to learn! Using a WKWebView is a horrible hack IMO. The usual reason for using WKWebView is that it has JIT Javascript, which JavascriptCore doesn't have, giving a worthwhile performance boost (maybe 10X). But that's not an issue here, as the JIT would just call the native C libxslt to do the work, and you can call that directly.

WKWebView supports the following APIs on both macOS and iOS: XSLTProcessor - https://developer.mozilla.org/en-US/docs/Web/API/XSLTProcessor That’s not XSLT 2, is it? (Is that available in JavascriptCore?)

What does the "Resubmit" link in their email do? (Are you an individual or a business?)

not many people would use it (well, drug dealers might). Let's also have a "coffee" purity tester where you put a couple of grains down the speaker hole and it tells you if it's 100% Arabica or whether it's been cut with baking soda.

You can use the "promotional text" field. It's not very prominent though.

Some years ago, there seemed to be a possibility with an external C library, but it was also mentioned that at a moment it was no more accepted by the App Store. Can you say more about that? The open-source libxslt is XSLT 1.0 only. I'm curious to know what XSLT 2 library you're referring to.

Somewhere there will be nfs-specific mount syscall documentation, but I can't immediately find it. (man mount_nfs is for the mount command, not the syscall.) I bet you need to pass some NFS-specific struct to mount's data argument.

Yes, me too. Be patient, it will catch up eventually.

This page is worth reading: https://developer.apple.com/documentation/apple-silicon/porting-just-in-time-compilers-to-apple-silicon describes how it works on MacOS. I believe that iOS likely works much the same, except crucially that our apps cannot get the required entitlement.

Working for me now.

FB14265010

Are you sure this worked on an unmodified iOS device? That seems unlikely to me. mmaping executable memory is specifically disallowed, with a very limited exception that Safari uses to JIT Javascript.

Which "boating app" are you using? iOS has a feature that can pause location updates when it thinks you have stopped moving (for power reasons, not security); whether this is enabled can be controlled by each app, but it defaults to ON: https://developer.apple.com/documentation/corelocation/cllocationmanager/pauseslocationupdatesautomatically Ask the developers of your app whether they set this property. A more recent, and related, feature is the "stationary" property of CLUpdate: https://developer.apple.com/documentation/corelocation/clupdate/4337718-stationary

Am I the only one who is getting this error message? No you're not the only one, it's borked for me too. Probably best to just wait for now, it will get fixed eventually.

See: https://developer.apple.com/forums/thread/744277