-
Notifications
You must be signed in to change notification settings - Fork 165
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
IRealmCollection SubscribeForNotifications not working!!! #3598
Comments
➤ PM Bot commented: Jira ticket: RNET-1144 |
How is |
The |
In any case, I've tried creating a simple project (I only built it in release, haven't packaged it in MSIX) and can't reproduce the behavior - can you create a repro case that we can use to further investigate. |
Thanks, I got it. |
I tried packaging a simple WPF app in MSIX and wasn't able to repro the issue you're describing. I've attached a zipped version of the project I created - I can package that, install it, and it works as expected - clicking the "Add item" button will immediately update the listview. If you can confirm whether it works for you and/or modify it so that it reproduces the problem, I can continue looking into it. |
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. |
What happened?
I used SubscribeForNotifications with IRealmCollection. After packaging the app into an MSIX for installation, I didn't receive any notifications when adding a new record. However, during local debugging, I could receive notifications.
Repro steps
Version
8.0
What Atlas Services are you using?
Local Database only
What type of application is this?
Other
Client OS and version
Windows 10 22H2 build 19045.4291
Code snippets
DataService.cs
ViewModel.cs
Stacktrace of the exception/crash you're getting
Relevant log output
The text was updated successfully, but these errors were encountered: