We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm setting up the uniffi for my application: https://github.com/toeverything/AFFiNE/blob/11-14-feat_android_native_module/packages/frontend/mobile-native/src/lib.rs
The basic FFI implementation works fine here: https://github.com/toeverything/AFFiNE/blob/965132593b4fcba8e35776730029d1c600013d89/packages/frontend/apps/android/App/app/src/main/java/app/affine/pro/MainActivity.kt#L11-L20
However, the uniffi call causes a SIGSEGV
uniffi
SIGSEGV
After some debugging, I found the RustBuffer() call here https://github.com/toeverything/AFFiNE/blob/11-14-feat_android_native_module/packages/frontend/apps/android/App/app/src/main/java/uniffi/affine_mobile_native/affine_mobile_native.kt#L246 is causing the SIGSEGV
RustBuffer()
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm setting up the uniffi for my application: https://github.com/toeverything/AFFiNE/blob/11-14-feat_android_native_module/packages/frontend/mobile-native/src/lib.rs
The basic FFI implementation works fine here: https://github.com/toeverything/AFFiNE/blob/965132593b4fcba8e35776730029d1c600013d89/packages/frontend/apps/android/App/app/src/main/java/app/affine/pro/MainActivity.kt#L11-L20
However, the
unifficall causes aSIGSEGVAfter some debugging, I found the
RustBuffer()call here https://github.com/toeverything/AFFiNE/blob/11-14-feat_android_native_module/packages/frontend/apps/android/App/app/src/main/java/uniffi/affine_mobile_native/affine_mobile_native.kt#L246 is causing theSIGSEGVThe text was updated successfully, but these errors were encountered: