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

Newly Added Field in Realm Getting Null #7857

Closed
rahul-kumawat-vts opened this issue Sep 1, 2023 · 2 comments
Closed

Newly Added Field in Realm Getting Null #7857

rahul-kumawat-vts opened this issue Sep 1, 2023 · 2 comments
Labels
Encryption:Off Frequency:Always More-information-needed More information needed from the reporter. The issue will autoclose if no more information is given. O-Community Repro:Always SDK-Use:Local T-Bug Waiting-For-Reporter Waiting for more information from the reporter before we can proceed

Comments

@rahul-kumawat-vts
Copy link

rahul-kumawat-vts commented Sep 1, 2023

How frequently does the bug occur?

Always

Description

In my project i have a RealmObject() class, I have added a new field in that class and install the fresh application in my phone but i am getting null value of newly added fields from Database. Can you please let me know why this issue happen.

Realm Version Using - io.realm:realm-gradle-plugin:10.16.0

Stacktrace & log output

No exception and error logs in logcat

Can you reproduce the bug?

Always

Reproduction Steps

  1. Already create RealmObject Class
  2. Add a New Field
  3. Run the application in any new device
  4. Getting null value from Realm database table.

Version

10.16.0

What Atlas App Services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

Android OS -12

Build environment

Android Studio version: Android Studio Flamingo | 2022.2.1 Patch 2
Android Build Tools version: com.android.tools.build:gradle:7.4.2
Gradle version: gradle-7.5

@rorbech
Copy link
Contributor

rorbech commented Nov 21, 2023

This sounds a bit like #7840 where incremental build was failing to trigger regeneration of all accessors correctly. Could you give it a try with the latest release?

@sync-by-unito sync-by-unito bot added the Waiting-For-Reporter Waiting for more information from the reporter before we can proceed label Nov 21, 2023
@sync-by-unito sync-by-unito bot added the More-information-needed More information needed from the reporter. The issue will autoclose if no more information is given. label Jan 9, 2024
Copy link

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Encryption:Off Frequency:Always More-information-needed More information needed from the reporter. The issue will autoclose if no more information is given. O-Community Repro:Always SDK-Use:Local T-Bug Waiting-For-Reporter Waiting for more information from the reporter before we can proceed
Projects
None yet
Development

No branches or pull requests

2 participants