-
Notifications
You must be signed in to change notification settings - Fork 65
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
[librealmc.so] array_direct.hpp - realm::IndexArray::_index_string_find_all_prefix #1588
Comments
Hi @chrisnkrueger Thank you for reporting this. Do you have the full stack trace? At least the part saying exactly what error is happening seems to be missing. |
@cmelchior Thanks for the fast reply. Unfortunately, the reports on the Google Play Console are limited. However, here is another error, which might be related:
Edit: |
Hi @chrisnkrueger Token prefix search like the example you show is supported. We are investigating what might be the cause for the crash. |
Hi @chrisnkrueger the issue is that the query string is malformed, any string parameter must be within apostrophes ('):" Try with |
Hi again @chrisnkrueger , if you don't want to use apostrophes you can pass the string as a parameter as shown in the documentation examples. By the way, are you able to reproduce the first crash? Do you have the sample data to reproduce it? |
@cmelchior I can reproduce the crash when I use the filter argument Unfortunately, I don't get the correct stacktrace from the crash dump when using ndk-stack. |
How frequently does the bug occur?
Sometimes
Description
We are seeing the following crashes reported on our Android App (distributed via Play Store).
Stacktrace & log output
Can you reproduce the bug?
No
Reproduction Steps
We started to use the search query in Realm, where the user can enter a search with limited characters to
^A-Za-z0-9
.Example:
Version
1.12.0
What Atlas App Services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
Android 10 - 14
Build environment
No response
The text was updated successfully, but these errors were encountered: