Trey t
418ffc7772
The XCUITest for gitea#2 (Suite11) was failing for reasons unrelated to the cache fix — actual bugs in the registration/onboarding code that real users probably hit too: 1. OrganicOnboardingSecureField + iOS 26 SecureField/autofill bug On iOS 26, tapping a SwiftUI SecureField with .textContentType(.password) doesn't reliably bring up the keyboard — the strong-password autofill panel steals focus. Fix: under --ui-testing, default the visibility toggle to ON so the field renders as a plain TextField (which has reliable focus). Real users are unaffected. 2. Email registration didn't propagate auth state Apple/Google sign-in paths called AuthenticationManager.shared.login(), but email-registration's onChange(viewModel.isRegistered) handler did not. As a result, AuthenticationManager.isAuthenticated stayed false through the entire onboarding flow. OnboardingState.completeOnboarding has an auth guard that silently no-ops when isAuthenticated is false, leaving users stuck on the firstTask screen forever (until a scenePhase event triggered checkAuthenticationStatus to re-sync from DataManager). Fix: call authManager.login(verified: false) when isRegistered flips true. Suite11 now passes 2/2 in 96-107s, exercising the full onboarding flow and asserting tasks appear on residence detail without restart. Refs gitea#2
This is a Kotlin Multiplatform project targeting Android, iOS, Web, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run Web Application
To build and run the development version of the web app, use the run configuration from the run widget in your IDE's toolbar or run it directly from the terminal:
- for the Wasm target (faster, modern browsers):
- on macOS/Linux
./gradlew :composeApp:wasmJsBrowserDevelopmentRun - on Windows
.\gradlew.bat :composeApp:wasmJsBrowserDevelopmentRun
- on macOS/Linux
- for the JS target (slower, supports older browsers):
- on macOS/Linux
./gradlew :composeApp:jsBrowserDevelopmentRun - on Windows
.\gradlew.bat :composeApp:jsBrowserDevelopmentRun
- on macOS/Linux
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform, Compose Multiplatform, Kotlin/Wasm…
We would appreciate your feedback on Compose/Web and Kotlin/Wasm in the public Slack channel #compose-web. If you face any issues, please report them on YouTrack.