Skip to content
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

Refresh issue on Android (dev) in 11.10.2 #6909

Open
ferrannp opened this issue Oct 24, 2024 · 5 comments
Open

Refresh issue on Android (dev) in 11.10.2 #6909

ferrannp opened this issue Oct 24, 2024 · 5 comments

Comments

@ferrannp
Copy link

How frequently does the bug occur?

Always

Description

Basically this: #5961.

@takameyer said:

I've tested with [email protected] and [email protected] and the issue doesn't exist. I guess the regression was only added within the v12 release.

But I see this crashing on React Native 0.73 and [email protected]. Could we make a patch like 11.10.2? 🙏 . cc @kneth

Stacktrace & log output

No response

Can you reproduce the bug?

Always

Reproduction Steps

Just refresh JS on Android.

Version

11.10.2

What services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

RN 0.73 and Realm 11.10.2

Build environment

Which debugger for React Native: ..

Cocoapods version

No response

Copy link

sync-by-unito bot commented Oct 24, 2024

➤ PM Bot commented:

Jira ticket: RJS-2912

@ferrannp
Copy link
Author

Still an issue in v11, wanted to fork but no idea how to build this to npm :D.

@kraenhansen
Copy link
Member

kraenhansen commented Nov 28, 2024

This might help? https://github.com/realm/realm-js/blob/v11/contrib/building.md

Are there any particular reason you're unable to upgrade to the latest version of the SDK?

Still an issue in v11

Any fix to this will have to come from the community.

@ferrannp
Copy link
Author

Hey! Thanks for answering. I tried to update to 12.x but got a lot of issues in my schemas and listeners so I assumed there a quite a few breaking changes there. Just wanted to point out that the latest 11.x has this issue and the fix seems pretty easy so I was just hoping for a quick 11.x patch version 😇

@kraenhansen
Copy link
Member

I assumed there a quite a few breaking changes there

It was a design goal of v12 to introduce as few breaking changes as possible - see release notes for the details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants