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
Always
Breaking issue in 12.6.0 User function argument sent to Atlas is wrapped in an Array
the problem is in this file, (idk where is this issue in the source repo) ./node_modules/realm/dist/bundle.react-native.js line ~7600
callFunction(name, ...args) { return this.callFunctionOnService(name, undefined, args); }
As you can see, the function received spread variable arguments, but then you passed it to callFunctionOnService as one array variable
callFunctionOnService
No response
Just install realm 12.6.0 in a react-native project
12.6.0
Atlas App Services: Functions or GraphQL or DataAPI etc
No
WSL Ubuntu on Windows
Which debugger for React Native: .. none
The text was updated successfully, but these errors were encountered:
User#callFunction
Successfully merging a pull request may close this issue.
How frequently does the bug occur?
Always
Description
Breaking issue in 12.6.0
User function argument sent to Atlas is wrapped in an Array
the problem is in this file, (idk where is this issue in the source repo)
./node_modules/realm/dist/bundle.react-native.js
line ~7600
As you can see, the function received spread variable arguments, but then you passed it to
callFunctionOnService
as one array variableStacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps
Just install realm 12.6.0 in a react-native project
Version
12.6.0
What services are you using?
Atlas App Services: Functions or GraphQL or DataAPI etc
Are you using encryption?
No
Platform OS and version(s)
WSL Ubuntu on Windows
Build environment
Which debugger for React Native: ..
none
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: