Add wasmJs target and support

[EpicSquid]

Using Ktor 3.x and Kotlin 2.0 I've added a wasmJs target for publishing so it can be used fully cross platform.

[Ingwersaft]

Hey, thanks for the contribution!

Looks like actions/upload-artifact#691 broke the pipeline. Could you switch to actions/upload-artifact@v4 in your branch please?

[EpicSquid]

Sure thing, sorry haven't been able to get to this yet. Will try again this week

[EpicSquid]

I know I've made some changes that may need rectifying, but now the build works correctly I wanted to see if tests pass in the pipeline.

[Ingwersaft]

Anyone with collaborator access to this repository can use these secrets and variables for actions. They are not passed to workflows that are triggered by a pull request from a fork.

You can tell that I don't use github very often :D

I pushed your changes so the pipeline runs with the secrets: #75

[henwoods]

I was just looking to work on bumping versions to fix the ktor compatiblity issues I'm also experience, but the work is already done here!

Any way we can get some movement on this 🙏

[Ingwersaft]

https://github.com/Liftric/cognito-idp/pull/75/checks fails during Build testapp and test request (iOS):

Testing failed:

Test session results, code coverage, and logs:
	/Users/runner/Library/Developer/Xcode/DerivedData/TestApp-bnlmepeuogcisibknrjooplcfvfa/Logs/Test/Run-TestApp-2025.05.22_12-22-07-+0000.xcresult

	Unable to Install “com.liftric.cognito.idp.TestApp”
	TestApp encountered an error (Failed to install or launch the test runner. (Underlying Error: Unable to Install “com.liftric.cognito.idp.TestApp”. This app cannot be installed because its integrity could not be verified. Failed to verify code signature of /var/db/appinstalld/Library/Caches/com.apple.mobile.installd.staging/temp.dnIRNG/extracted/TestApp.app : 0xe800801c (No code signature found.)))

As a linux user I can't debug it and no apple user at our place has time for it right now.

[PruszynskiJakub]

It's probably related to profile provisioning. Although I am quite new on iOS. Could help @Ingwersaft ?
Any way we can get some movement on this 🙏

[PruszynskiJakub]

Main Causes and Solutions
Missing/Invalid Code Signature

The error 0xe800801c (No code signature found) means the app binary is not correctly signed. All iOS apps must be signed with a valid certificate and provisioning profile.

Possible Reasons:

• The app was built without code signing, or the signing identity was not properly configured.

• The provisioning profile used does not match the device or the app bundle identifier.

• The certificate used for signing has expired or is not installed on your machine.

How to Fix:

• Clean and Rebuild: In Xcode, go to Product > Clean Build Folder, then rebuild the project to ensure the signature is applied correctly.

• Check Signing Settings: In your Xcode project settings, verify that:

• The correct Team is selected under Signing & Capabilities.

• The right Provisioning Profile and Signing Certificate are assigned.

• Automatic signing may help (check "Automatically manage signing").

• Device Trust Issues: If you are installing a development build, make sure the device trusts your developer certificate:

• On the device, go to Settings > General > Device Management (or Profiles & Device Management) and trust your certificate.

• Profile/Certificate Expiry: Ensure neither the provisioning profile nor the certificate has expired. Renew or re-download as needed.

• Rebuild and Reinstall: After adjustments, rebuild the app and reattempt installation.

• Delete Old App: Sometimes, deleting the previously failed installation from the device helps before retrying.

If using CI/CD or external tools

• Make sure the .ipa or .app is correctly signed before distribution.

• If exporting for Ad Hoc or Enterprise distribution, include the proper provisioning profile.

[ghost]

Also keen for this change 🙏

Is this the wrong thread to be debugging iOS build issues in though? The issue is for adding wasmJs target.

[JakubPruszynski]

@chris-hatton-tipmi I believe that ktor 3+ is the main root change, wasm support is an extra

[benjohnde]

@Khartris did the migration to modern versions. If you are still interested in bringing this to life, I would recommend to rebranch from the current master after #76 was merged to enable wasmJs @EpicSquid.

[EpicSquid]

Noted, thanks. I'll take a look and see if I can get that sorted. Appreciate the dependency update being completed already.

[benjohnde]

@EpicSquid btw huge thanks for tackling this!

[EpicSquid]

New PR submitted with the updated changes. Let me know if you need anything else: #78