fix: WASM MIME type error by specifying it in Info.plist template

[michaelkamphausen]

Platforms affected

iOS

Motivation and Context

Fixes #1370 where WebAssembly cannot be loaded in iOS production build due to the error "Unexpected response MIME type. Expected 'application/wasm'". The error causes a blank app screen and prevents any user interaction.

Description

I added UTExportedTypeDeclarations to the Info.plist template file, specifying the expected MIME type for loading WASM files.

Testing

I modified my project's Info.plist file by adding the UTExportedTypeDeclarations key and value as shown in the commit, built and ran my project on the device, and verified that the app loads and is displayed as expected.

The automated tests don't run on my macOS version as it does not match CordovaLibTests’s deployment target. I don't know how to get the tests running.

Checklist

• I've run the tests to see all new and existing tests pass
• I added automated test coverage as appropriate for this change
• Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
• If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
• I've updated the documentation if necessary

[codecov-commenter]

Codecov Report

Merging #1374 (f10ee32) into master (a1f3ace) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1374   +/-   ##
=======================================
  Coverage   78.25%   78.25%           
=======================================
  Files          15       15           
  Lines        1789     1789           
=======================================
  Hits         1400     1400           
  Misses        389      389           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dpogue]

I'm curious if this also works if you use UTImportedTypeDeclarations as the key

I don't think we want to declare all Cordova apps as owners of the WebAssembly file type by default, so UTExportedTypeDeclarations seems like it might be the wrong key to use. Even with that though, I think injecting this when needed using config-file in config.xml for your app is probably a better choice that unconditionally including this declaration in the template for all Cordova apps.

[michaelkamphausen]

I like your idea of using UTImportedTypeDeclarations key instead! I tested it and I can confirm that it works as well.

I understand there are differing views on whether loading WebAssembly code should be supported by default or only when needed.

I would argue for making this a default because I assume quite a few developers will be unaware of the problem until it suddenly occurs in their Testflight or release build. The cause is not easy to find, because the problem does not seem to occur in debug builds, which makes debugging difficult. This could be confusing and will cost time. At the same time, I don't see any downside how the UTImportedTypeDeclarations entry could cause problems.

Nevertheless, at least the documentation should point out the WASM loading error in release builds and explain how to fix it when needed using config-file in config.xml.

[mohammadrafigh]

Maybe it's optimistic, but it would be great if we could have a script to detect if the code is using WASM or not, then warn users to enable usage of WASM in config.xml. But for now this could be enough to somehow easily enable WASM support in config.xml. Putting all those config lines in config.xml is not a minimal way to enable WASM. Maybe a boolean preference like EnableWASM makes sense.

<preference name="EnableWASM" value="true" />

[erisu]

LGTM