-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android build fails #10
Comments
This might mean that the code generation didn't run. 🤔
I'm not at all familiar with Expo, unfortunately, but in the example app in this repo, codegen is triggered in |
Hi @Johennes. Thanks for the quick response. Looks like the code is being built automatically in If I copy over the files after a first run, the Android build works:
I would provide a PR, but I couldn't figure out where the codegen directory is (or can be) specified inside build process of the library. Any idea? Regards, Oliver |
Oh, interesting. The output directories for codegen are specified in package.json. "codegenConfig": {
"name": "RNReactNativeMatrixSdkSpec",
"type": "all",
"jsSrcsDir": "src",
"outputDir": {
"ios": "ios/generated",
"android": "android/generated"
},
"android": {
"javaPackageName": "com.unomed.reactnativematrixsdk"
},
"includesGeneratedCode": true
}, It's interesting that they're being expected in another location in your build. 😵💫 Could you check if changing the We made a fix in uniffi-bindgen-react-native to handle non-standard codegen output dirs a while ago that hasn't been consumed in react-native-matrix-sdk yet. However, I'm not sure that's related. |
Hi @Johennes, I've changed the It seems that React Native expects the files at However, I couldn't find the right place where the build process creates |
I think you might have to trigger codegen manually after changing When I apply the following diff, I'm getting the generated code under the expected path.
I'm still confused that I'm also not sure why I haven't seen this in the project I'm consuming react-native-matrix-sdk but maybe it's because I'm not on the latest RN version there. |
Hi @Johennes . Thanks for merging the PRs. Could you create a new release, please? Since everything is included in the NPM package, I think someone just needs |
Sorry, I've been meaning to do it yesterday already but I was having some build issues locally. Releasing currently requires building matrix-rust-sdk in release mode locally which takes ... long. I've just landed #15 which was needed to compile the x86-64 Android target on my machine. Will start the release build now. Hopefully this can happen on the CI in future. |
Just pushed 0.3.0 to npm. Let me know if this doesn't fix your issues and thanks once more for helping to fix this. |
Hello.
I'm trying to build the library for iOS and Android. iOS build works perfectly fine by using Expo.
I was wondering, if I can also do a build for Android as well, but that fails with the following message:
For reproducing this, I've added a small repo here:
https://github.com/olliiiver/matrix_rust_sdk_test
It seems the build process is missing a build step. How can I fix this?
Any help would be greatly appreciated!
Regards,
Oliver
The text was updated successfully, but these errors were encountered: